fire hd 8 bootloop after installing custom rom - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

fire hd 8 bootloop after installing custom rom - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

Well, I made a Fire HD 8 2018 custom ROM successfully but it went into boot loop that all it does show Amazon logo and I have a dmesg log attached and it was a kernel error, id like to mention @k4y0z to help me out to figure out what's wrong with the kernel. and i think that something went missing or it could not initialize. I copied the log from recovery.

Kaijones23 said:
Well, I made a Fire HD 8 2018 custom ROM successfully but it went into boot loop that all it does show Amazon logo and I have a dmesg log attached and it was a kernel error, id like to mention @k4y0z to help me out to figure out what's wrong with the kernel. and i think that something went missing or it could not initialize. I copied the log from recovery.
Click to expand...
Click to collapse
The log you attached is from recovery, so it won't help finding issues with the ROM.
You can try to get /proc/last_kmsg to see if that shows anything.
Otherwise you may need to attach a serial console to UART.
Not sure if kernel-logging on UART is enabled in amonet-karnak though.
Alternatively you can try getting adb to work on your ROM to see if you can get a logcat and dmesg.
Make sure you build an eng-kernel so adb is enabled by default.
You may also need to add
Code:
sys.usb.ffs.aio_compat=1
to your default.prop

k4y0z said:
The log you attached is from recovery, so it won't help finding issues with the ROM.
You can try to get /proc/last_kmsg to see if that shows anything.
Otherwise you may need to attach a serial console to UART.
Not sure if kernel-logging on UART is enabled in amonet-karnak though.
Alternatively you can try getting adb to work on your ROM to see if you can get a logcat and dmesg.
Make sure you build an eng-kernel so adb is enabled by default.
You may also need to add
Code:
sys.usb.ffs.aio_compat=1
to your default.prop
Click to expand...
Click to collapse
well, it doesn't boot up because it shuts down by itself. what happened is that, when I started it up and it shows the Amazon logo and shuts down. I can be able to boot into recovery. what I cant find is proc/last_kmsg. and how can i do the UART?

Kaijones23 said:
well, it doesn't boot up because it shuts down by itself. what happened is that, when I started it up and it shows the Amazon logo and shuts down. I can be able to boot into recovery. what I cant find is proc/last_kmsg. and how can i do the UART?
Click to expand...
Click to collapse
Look in /sys/fs/pstore/console-ramoops if there is no /proc/last_kmsg.
If it crashes, then hold the volume-button so it will reboot directly into recovery after crashing.
You should get the last kernel log there to see what caused the crash.
I don't know where the UART is on the karnak, since I don't have the device.

I don’t see that file in the recovery too. Well I reverted the changes from adding ambient capabilities to the kernel and. Removed all that by extracting a fresh kernel from amazon and then I had to rebuild the rom and added some overrides that you told me to add. If I had to I can use the prebuilt kernel as a fallback but what are the issues building with the prebuilt kernel
Sent from my iPhone using Tapatalk

Kaijones23 said:
I don’t see that file in the recovery too. Well I reverted the changes from adding ambient capabilities to the kernel and. Removed all that by extracting a fresh kernel from amazon and then I had to rebuild the rom and added some overrides that you told me to add. If I had to I can use the prebuilt kernel as a fallback but what are the issues building with the prebuilt kernel
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
well I got the file and here you go @k4y0z

Kaijones23 said:
well I got the file and here you go @k4y0z
Click to expand...
Click to collapse
That's still the log from your recovery.
You need to get the device to reboot into recovery right after it crashes, so you can get the log from the crash.

Ok so I tried with prebuilt kernel, it stays on amazon logo and when I tried with the stock boot img with symlinks to fosinit and fossvc jars to linage os platform. But it still stays on amazon logo for the prebuilt and stock boot img. On the built kernel, it crashes and I can’t get logs. I’m trying to find a way to patch it with carliv’s image kitchen. But I don’t know what init files I can modify from my tree
Sent from my iPhone using Tapatalk

@k4y0z I won’t be able to get last_kmsg and ram-oops logs. I don’t know why
Sent from my iPhone using Tapatalk

@k4y0z I won’t be able to get last_kmsg and ram-oops logs. I don’t know why
Sent from my iPhone using Tapatalk

Code:
deleted. Posted twice by accident

I’m having issues booting with the custom rom with built kernel because it panics at startup and shuts down with built kernel. What methods I have tried is that I used the built kernel and it stops at amazon logo and shuts down. When I use prebuilt kernel, it stays on amazon logo. When I use its stock boot img from fire os with symbolic links it doesn’t boot and stays on amazon logo. I’m stuck at this process that it doesn’t boot up and I can’t get last_kmsg or ramoops. It’s making me struggle and I’d like @k4y0z to help me out and can fork my tree or authored it to help me what is wrong with my tree. I really can’t figure out but I am able to flash stock fire os back and it still has root access and twrp. I think the main cause of the problem is the verified boot or something. My tree is updated. https://github.com/488315/android_device_amazon_karnak. I tried adb devices on the boot process when it is on the amazon logo and it doesn’t show up on there. I tried to use default prop overrides and well it doesn’t show up too. Honestly I really don’t understand what is going on and I really need help to test this rom out. The kernel source for this device is incomplete and i have experience with building ROMs and this took me days than usual. I made a rom by using otapackage and it is block based. I’ve copied kernel modules and vendor files and some bin files and lib from fire os. When I made this rom, everything is included in this rom that are needed. I hope you guys have a good easter and I start school upcoming Monday and I will have a little time working on this rom and figuring it out to make it boot up. This device is not easy. Thanks

fire hd 8 2018 boots into fast-boot after installing custom ROM.
Kaijones23 said:
@k4y0z I won’t be able to get last_kmsg and ram-oops logs. I don’t know why
Click to expand...
Click to collapse
@k4y0z, well I see some progress in this code after I remove this line,
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait,verify
to
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait
it boots into fastboot after installing custom ROM.
the files I have attached is:
ramdisk.zip rootdir from my device tree
boot.zip boot.img from lineage os before it was compiled.
there is something is preventing the ROM from booting up because I won't be able to get the logs.
if you want to see the fire HD 8's extracted boot image, it is posted on my GitHub here.
the problem I think it is an issue with init files.
thank you for your help. I know you dont have a fire hd 8 and i want this thing to boot into lineage.

Kaijones23 said:
@k4y0z, well I see some progress in this code after I remove this line,
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait,verify
to
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait
Click to expand...
Click to collapse
Yes, you definitely want to disable dm-verity.
Kaijones23 said:
it boots into fastboot after installing custom ROM.
Click to expand...
Click to collapse
If it (re)boots into fastboot, you are probably missing some kernel-patches/features

k4y0z said:
Yes, you definitely want to disable dm-verity.
If it (re)boots into fastboot, you are probably missing some kernel-patches/features
Click to expand...
Click to collapse
Ok so I have been using prebuilt kernel and then well if I use the original kernel amazon uses, I can’t boot it up. It just bootloops. What patches do I need to add from the kernel tree l, I can’t build a rom Amazon’s script because it has issues. I’ll try once more with Amazon’s build script. How can I use it properly so it can successfully compile
Sent from my iPhone using Tapatalk

Hello I was able to compile the Amazon’s fire hd kernel with the script that’s included with the source. I don’t know what modifications to make it support android pie
Sent from my iPhone using Tapatalk

you could start with cherry-picking commits to get it booting and then go from there
mostly you are gonna be building up from scratch and cherry picking commits from other mtk devices
its not impossible I know @k4y0z
has los16 booting on suez but I am pretty sure it doesn't do much else yet

Legitsu said:
you could start with cherry-picking commits to get it booting and then go from there
mostly you are gonna be building up from scratch and cherry picking commits from other mtk devices
its not impossible I know @k4y0z
has los16 booting on suez but I am pretty sure it doesn't do much else yet
Click to expand...
Click to collapse
@k4y0z well since I set to SELinux to permissive, it has logcat and I proveded it in this attachment. when I build the kernel with amazons script and added some patches to my kernel from your tree, it doesn't boot up like it shows at Amazon logo and shuts down.
how would you be able to get the built kernel to boot up?

Legitsu said:
you could start with cherry-picking commits to get it booting and then go from there
mostly you are gonna be building up from scratch and cherry picking commits from other mtk devices
its not impossible I know @k4y0z
has los16 booting on suez but I am pretty sure it doesn't do much else yet
Click to expand...
Click to collapse
That's not entirely accurate, I have WiFi working and audio partially
But yes, getting it to boot is something entirely different from getting it to actually be usable.
Kaijones23 said:
@k4y0z well since I set to SELinux to permissive, it has logcat and I proveded it in this attachment. when I build the kernel with amazons script and added some patches to my kernel from your tree, it doesn't boot up like it shows at Amazon logo and shuts down.
how would you be able to get the built kernel to boot up?
Click to expand...
Click to collapse
I don't know why your kernel doesn't boot, but the log shows you are missing some stuff as I have said before.
You probably need ambient capabilities and hwbinder patches.

k4y0z said:
That's not entirely accurate, I have WiFi working and audio partially
But yes, getting it to boot is something entirely different from getting it to actually be usable.
I don't know why your kernel doesn't boot, but the log shows you are missing some stuff as I have said before.
You probably need ambient capabilities and hwbinder patches.
Click to expand...
Click to collapse
ahh I was just going by why I saw in your git
nice nice

Related

[Q] Development for the M.O.J.O

Currently the M.O.J.O has been a very unsuccessful device and there hasn't been any recent development. I would like to give a try at a few things such as a custom recovery
I am asking for someone to provide with me with the output of the following commands
Start adb shell
Code:
cat proc/iomem > iomem.txt
Code:
cat proc/partitions > partitions.txt
Code:
getprop > prop.txt
I've attached a test cwm recovery.img DO NOT FASTBOOT FLASH RECOVERY!!! use the below command to test the image
Code:
fastboot boot recovery.img

Hi,
Thanks heaps for helping dev on the mojo!
I'm keen to help!
Done.. I"ll try the image now.
./fastboot-linux -i 0x0738 devices
15C40C1C30400000012FC8380 fastboot
./fastboot-linux -i 0x0738 boot recovery.img
downloading 'boot.img'...
OKAY [ 0.375s]
booting...
OKAY [ 0.001s]
finished. total time: 0.377s
Click to expand...
Click to collapse
It does nothing for about a minute, then the blue light comes on the screen says 'mode not supported', tried on a monitor (with a HDMI to DVI) same 'mode not supported' then no signal.
Not sure how you would get debugging info out ... that's been the main problem
Anyway, if you need any more info or test, just ask.

gwaldo said:
Hi,
Done.. I"ll try the image now.
Click to expand...
Click to collapse
Thanks it helps a lot with the device tree. How did the recovery turn out?

Unjustified Dev said:
Thanks it helps a lot with the device tree. How did the recovery turn out?
Click to expand...
Click to collapse
Didn't do anthing, or at least I couldn't see it on my TV nor monitor :/

gwaldo said:
Didn't do anthing, or at least I couldn't see it on my TV nor monitor :/
Click to expand...
Click to collapse
Thanks it could be a kernel issue I'm working on kexec hardboot I'm going to remove that for now and build again.
edit: Attached new image as well as a new adb and fastboot binary for you with adb and fastboot id added
https://github.com/TeamRegular/android_system_core/commit/effaa8a925b68651dbb1a0d50cffb81e57df9f5d
I replaced mine in /usr/bin/ with these and they still work as normal for me.

Unjustified Dev said:
Thanks it could be a kernel issue I'm working on kexec hardboot I'm going to remove that for now and build again.
edit: Attached new image as well as a new adb and fastboot binary for you with adb and fastboot id added
https://github.com/TeamRegular/android_system_core/commit/effaa8a925b68651dbb1a0d50cffb81e57df9f5d
I replaced mine in /usr/bin/ with these and they still work as normal for me.
Click to expand...
Click to collapse
Wow, I didn't even know fastboot had a github, you're very pro sir! :good:
I run it now:fingers-crossed:
using your exe (on my 32bit Mint linux 17):
./fastboot -i 0x0738 boot recovery-v2.img
downloading 'boot.img'...
OKAY [ 0.376s]
booting...
OKAY [ 0.001s]
finished. total time: 0.378s
Click to expand...
Click to collapse
But again same result

gwaldo said:
Wow, I didn't even know fastboot had a github, you're very pro sir! :good:
I run it now:fingers-crossed:
Click to expand...
Click to collapse
You can build those in an android environment that's actually from the source you would use to build a full rom I just forked the tree from CyanogenMod added the id and compiled it.

Unjustified Dev said:
You can build those in an android environment that's actually from the source you would use to build a full rom I just forked the tree from CyanogenMod added the id and compiled it.
Click to expand...
Click to collapse
Not sure what else to do, to get into the existing mojo's recovery, is pretty hit and miss for me (I get unsupported display a lot until it work) so not sure if that's normal... i'm a android dev noob, so don't really know how to use adb to debug the boot image.
Not sure if having a usb keyboard/mouse plugged in will help?
Edit:
Also the nvidia shield (Tegra4) is similarly spec'ed but not sure about the HW components.
It is a well documented and hacked device.
I'm sure so of what they do is applicable to mojo also?

gwaldo said:
Not sure what else to do, to get into the existing mojo's recovery, is pretty hit and miss for me (I get unsupported display a lot until it work) so not sure if that's normal... i'm a android dev noob, so don't really know how to use adb to debug the boot image.
Not sure if having a usb keyboard/mouse plugged in will help?
Click to expand...
Click to collapse
You should be able to run adb reboot recovery while the device is booted.
edit to your edit: The shield work is not applicable to the mojo but I have worked with the shield as well as ported cwm easily I'm wondering why this img won't boot I've seen the troubles in the other thread. I'm thinking maybe install the image to your recovery partition and adb reboot recovery it will not brick the device as the recovery image is safe on a partition that doesn't effect the booting process the boot partition on the other hand I would never fastboot flash it without testing if it boots first. I'm wondering if the img is too big for the partition maybe. I'm not sure the partition is 8mb the image is 7.6 I'm going to change the compression and see if it boots. You also no longer need the -i 0x0738 when using fastboot
Last edit could you pull proc/config.gz

Unjustified Dev said:
You should be able to run adb reboot recovery while the device is booted.
edit to your edit: The shield work is not applicable to the mojo but I have worked with the shield as well as ported cwm easily I'm wondering why this img won't boot I've seen the troubles in the other thread. I'm thinking maybe install the image to your recovery partition and adb reboot recovery it will not brick the device as the recovery image is safe on a partition that doesn't effect the booting process the boot partition on the other hand I would never fastboot flash it without testing if it boots first. I'm wondering if the img is too big for the partition maybe. I'm not sure the partition is 8mb the image is 7.6 I'm going to change the compression and see if it boots. You also no longer need the -i 0x0738 when using fastboot
Last edit could you pull proc/config.gz
Click to expand...
Click to collapse
I think it is booting, I just can't get a working display.
With a keyboard I can boot your recovery image and do a ALT Printscreen O and it turns off as expected.
I know a few of these keys from here: http://forum.xda-developers.com/showpost.php?p=54517256&postcount=32
I'll get that file for you now, I don't have adb set up.

gwaldo said:
I think it is booting, I just can't get a working display.
With a keyboard I can boot your recovery image and do a ALT Printscreen O and it turns off as expected.
I know a few of these keys from here: http://forum.xda-developers.com/showpost.php?p=54517256&postcount=32
I'll get that file for you now, I don't have adb set up.
Click to expand...
Click to collapse
Thanks I compared the defconfig to the one in the stock source and it was different compiling again.

Unjustified Dev said:
Thanks I compared the defconfig to the one in the stock source and it was different compiling again.
Click to expand...
Click to collapse
I'm running this update mojo-signed-ota-MO0202-WW.zip
from ftp://86.54.116.234/pub/software/mojo/firmware/
I think the kernel src version is from the first firmware update (mojo-signed-ota-MO0110-WW.zip) or it could be even before that.
I think the problem (maybe just mine) is I can't get a display in recovery with out a lot of F'ing around.. ie: randomly pressing home up/down ALT PRNTSCRN I etc... but like I said, your image does work as it responds to ALT PRNTSCN O
---------- Post added at 01:49 PM ---------- Previous post was at 01:33 PM ----------
Unjustified Dev said:
Thanks I compared the defconfig to the one in the stock source and it was different compiling again.
Click to expand...
Click to collapse
SH!T IT WORKS!!!
I couldn't get a display, so I ran it through my HDMI capture device, not expecting to record anything any it worked!!!
I'm uploading a vid now!
Congrats dude! you did it!

gwaldo said:
I'm running this update mojo-signed-ota-MO0202-WW.zip
from ftp://86.54.116.234/pub/software/mojo/firmware/
I think the kernel src version is from the first firmware update (mojo-signed-ota-MO0110-WW.zip) or it could be even before that.
I think the problem (maybe just mine) is I can't get a display in recovery with out a lot of F'ing around.. ie: randomly pressing home up/down ALT PRNTSCRN I etc... but like I said, your image does work as it responds to ALT PRNTSCN O
Click to expand...
Click to collapse
Here's the change https://github.com/TeamRegular/andr...mmit/e82e271131d30290022f301b70089cf2fb9224d3
It's also enabled on the shield I can't remember but it looks like I did it when I worked on the shield as well since it's not enabled in the defconfig they give us it's probably enabled in their nvidia source builds I can't remember how all that works it's been a while since I had shield source downloaded but hopefully this is the problem.

Unjustified Dev said:
Here's the change https://github.com/TeamRegular/andr...mmit/e82e271131d30290022f301b70089cf2fb9224d3
It's also enabled on the shield I can't remember but it looks like I did it when I worked on the shield as well since it's not enabled in the defconfig they give us it's probably enabled in their nvidia source builds I can't remember how all that works it's been a while since I had shield source downloaded but hopefully this is the problem.
Click to expand...
Click to collapse
I'll test it out, but your previous image works, my TV nor monitor likes the resolution (guessing).
Any chance of defaulting to a low res? or booting into a safe mode?

gwaldo said:
I'll test it out, but your previous image works, my TV nor monitor likes the resolution (guessing).
Any chance of defaulting to a low res? or booting into a safe mode?
Click to expand...
Click to collapse
I guess I would have to switch to twrp recovery I'm not sure what theme would fit but I added the size for mojo already It's just a matter of building it. Honestly most of the time twrp display code works better than cwm.
https://github.com/TeamRegular/android_bootable_recovery/commits/android-4.4

Here's the video, just hitting home and up/down keys.
https://www.youtube.com/watch?v=5A4yDR2Z_GU
Unjustified Dev said:
I guess I would have to switch to twrp recovery I'm not sure what theme would fit but I added the size for mojo already It's just a matter of building it. Honestly most of the time twrp display code works better than cwm.
https://github.com/TeamRegular/android_bootable_recovery/commits/android-4.4
Click to expand...
Click to collapse
It could be my TV/monitor is just old... but it's strange I don't have a problem with the MOJO/laptop etc.
If you build twrp, I'm happy to test it out also.

gwaldo said:
Here's the video, just hitting home and up/down keys.
https://www.youtube.com/watch?v=5A4yDR2Z_GU
It could be my TV/monitor is just old... but it's strange I don't have a problem with the MOJO/laptop etc.
If you build twrp, I'm happy to test it out also.
Click to expand...
Click to collapse
So this is the first booting just not outputting to screen very strange I'll look into it. I'll compile twrp now it will take over an hour to build I have to setup device to compile in omni rom environment. I'll pm you the build.

Unjustified Dev said:
So this is the first booting just outputting to screen very strange I'll look into it. I'll compile twrp now it will take over an hour to build I have to setup device to compile in omni rom environment. I'll pm you the build.
Click to expand...
Click to collapse
cwm-recovery.img also boots.
Really strange that I can't see a display but I can record the HDMI output on my AverMedia Capture HD II C285 as it's really sensitive to HDMI.
Maybe a frequency/refresh rate setting?
With the MOJO's recovery menu on my monitor I get:
MODE NOT SUPPORTED
H: 67.5KHZ
V: 60.0HZ
With your firmware:
MODE NOT SUPPORTED
H: 67.2KHZ
V: 59.7HZ
My TV is PAL, if that helps.
I'm guessing because the MOJO has no screen it's not sending a 100% correct HDMI stream.
Whatever the issue is, it's also in the default recovery.
Anyway, I'm sure others will try out your recovery image and we'll get feed back.
No problem, happy to test it out

gwaldo said:
cwm-recovery.img also boots.
Really strange that I can't see a display but I can record the HDMI output on my AverMedia Capture HD II C285 as it's really sensitive to HDMI.
Maybe a frequency/refresh rate setting?
With the MOJO's recovery menu on my monitor I get:
MODE NOT SUPPORTED
H: 67.5KHZ
V: 60.0HZ
With your firmware:
MODE NOT SUPPORTED
H: 67.2KHZ
V: 59.7HZ
My TV is PAL, if that helps.
I'm guessing because the MOJO has no screen it's not sending a 100% correct HDMI stream.
Whatever the issue is, it's also in the default recovery.
Anyway, I'm sure others will try out your recovery image and we'll get feed back.
No problem, happy to test it out
Click to expand...
Click to collapse
I'll take a look into some later commits from nvidia git the mojo kernel is quite outdated. I found last merged commit on this page
I tried to pick each one and ended up with a ton of issues I will try again in the next few days doing page by page only and building
https://github.com/somcom3x/android_kernel_nvidia_tegratab/commits/cm-11.0?page=24

gwaldo said:
Here's the video, just hitting home and up/down keys.
https://www.youtube.com/watch?v=5A4yDR2Z_GU
It could be my TV/monitor is just old... but it's strange I don't have a problem with the MOJO/laptop etc.
If you build twrp, I'm happy to test it out also.
Click to expand...
Click to collapse
Interesting, im using a monitor which supports many formats and it wasnt able to pick up when i tried my hand at CWM, alas i didnt have a screen capture device so i just assumed it was something wrong with foxconn's programming/setup than just graphics not displaying properly.

Problems booting the open source kernel on the shield 2017

hi,
this was the first time compiling a kernel from android source. I'm actually a java and app dev, so this was actually new to me.
I wanted to have full ntfs support and maybe some other features on my shield so i thought i'll give it a try.
the first thing i tried was pulling the whole android source code from the nvidia git server. Then I followed the instructions except i changed "mp dev" to "mp bootimage -j5" to just build the kernel. (I also did no modifications to the kernel). All went well and I got the boot image.
I used this repo: rel-24-uda-r1-partner.
I flashed the boot image with fastboot, but when it boots up, the nvidia sign comes and after some time I get a message with a red exclamation mark, which says that the partitions are corrupted or something like that. Then I get a black screen.
I also dont want to open up the device to access the uart to read out the kernel messages.
I dont know what else to do. Am I missing something? Does the open source kernel even work on stock android rom?

have u tried wiping the data partition?

yes i have

Take a look at the last few posts on this thread https://forum.xda-developers.com/sh...ecovery-twrp-shield-android-tv-t3510456/page4

so do you mean i have to use a another toolchain?

Jahusa said:
so do you mean i have to use a another toolchain?
Click to expand...
Click to collapse
I believe so

It works now. I copied the kernel from the repo into a another folder, set the env variables for the cross compilers and compiled it.
With the help of some threads in the nvidia forum and google, i got everything compiled.
The kernel boots now. But there's still the red sign at boot. I have to figure it out later.
Edit: OK, i think I got it now. To remove the annoying sign, I have to somehow disable the boot verification.

@AndroidUser00110001 did you sign your trwp recovery image when you created it. If you didn't, then it would also trigger the boot verification. That's what I think.
Also thanks for your recovery image

That warning pops up once you unlock bootloader.
Jahusa said:
@AndroidUser00110001 did you sign your trwp recovery image when you created it. If you didn't, then it would also trigger the boot verification. That's what I think.
Also thanks for your recovery image
Click to expand...
Click to collapse

EFIDroid

Just wondering if anyone has looked into this, and what it could possibly mean for our device if we could be merged. Apparently there's no need for special kernel modules, bootloader edits, or KEXEC, and I think it would be pretty cool to be able to use multi ROM to boot back and forth between stock and AOSP.

Why don't you explain what this is and provide a few links?

lafester said:
Why don't you explain what this is and provide a few links?
Click to expand...
Click to collapse
https://www.xda-developers.com/efidroid-is-a-second-stage-bootloader/
This article was the first I'd heard of it. But it does seem like it might be something easy to implement. It's basically multi ROM, but without all the requirements.

Looks interesting.

is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?

gecko702 said:
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
Click to expand...
Click to collapse
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...

This is very, very interesting. I love the thought of just using LineageOS or RR for everyday things and then just switching to stock when I want to use media and enjoy the fantastic sound.
I'm not a developer, but I'd like to help/contribute in any way possible if someone's working on bringing unofficial support to the Axon 7.

jimbo77 said:
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
Click to expand...
Click to collapse
Very true. However, it makes ROMs easier to port and for more people to test, as then people can try them out without wiping their phone each time they want to try.

I was able to port and build right up until the last step where you generate lk.img and fastboot it to the phone. I'm running Linux inside a virtual machine and it doesn't seem to want to communicate, though adb does work.
I might try on the weekend to boot linux off a hard drive and see if it will work..
In the mean time, if someone else wants to try to build, it's really simple just follow these two guides:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Getting-Started
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device

I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?

twoi said:
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
Click to expand...
Click to collapse
Did you try this fix for arm64 devices?
https://github.com/efidroid/projectmanagement/issues/89
Seems you need to dump aboot to check what's the correct address for LK to boot.
Edit: also did you try using freeza Beastmode boot.img? Probably that's better

Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..

twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
Yeah that's he creator of Efidroid... Why don't you reply to that issue tracker and add the Axon 7 to the list of devices that don't boot because of the arm64 arch

twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
yes you are on right track

twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something

Druboo666 said:
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Click to expand...
Click to collapse
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.

twoi said:
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
Click to expand...
Click to collapse
you should contact with the dev he may help you OP3 and A7 got same chipset so yeah it will help

I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.

twoi said:
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
Click to expand...
Click to collapse
you can contact @npjohnson or @m1cha with your compiled LK or boot maybe they can help
as they have fix Nexus 6P LK with no uefi boot

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.

Onn 100003562 TWRP

This thread is presently about the development of a TWRP port to these devices.
The build is not yet working!
I am in the process of porting TWRP to my 3562 mostly out of pure spite for this stupid device. This thread is mostly for collecting my development process, for anyone who is interested, or wants to help.
Presently, TWRP will boot properly, and does function apart from UI issues and generally not being able to mount partitions correctly.
The UI draws in portrait mode (USB port at the top), but the touch interface responds in landscape mode (USB port on the right). This is very annoying, but it is still usable, so I haven't looked too far into it.
It seems to mount boot and userdata partitions okay, /sdcard is full of garbage data (encrypted? bad mount flags?), /system will not mount at all.
First order of business is to get /system mounted. It looks like this is related to vbmeta, so I have to sort out how to properly wipe the vbmeta on this device.
Here is my current image, if anyone is interested in trying it out: https://drive.google.com/file/d/1kMvKvocKY6AWRR-xkXIwisv27TmF6xcP/view?usp=sharing
I'll keep this updated as I keep working. As always, any input is greatly appreciated.

@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?

rolenthedeep said:
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
Click to expand...
Click to collapse
Thanks for moving, we were a bit OT in other thread. Yes the boardconfig.mk is for building from source. Does no good when using kitchen, I was just showing you an example of where and how rotation was handled. I still haven't followed up on changing rotation and touch input using kitchen, just got home from another heart catheterization. The only way to get a fully working fully functional twrp is to build from source, but without source code AIK is an awesome alternative. I just can't remember if we can change rotation and touch input in de-compiled img. We can ask @osm0sis if it is possible to edit recovery rotation via AIK. If you've not done so already, check out his work here on XDA. There are a lot of useful tools and scripts authored by him and a wealth of android knowledge that you can only benefit from reading.

Haven't ever messed with TWRP rotation myself, sorry. I'm sure it's something you can Google and find out though.

@rolenthedeep look at this may be helpful with rotation

I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.

mpalpha said:
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
Click to expand...
Click to collapse
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.

tek3195 said:
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
Click to expand...
Click to collapse
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.

mpalpha said:
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
Click to expand...
Click to collapse
I thought I was replying to someone else, but same applies. You're wanting to port one using kitchen the best place to start is here:
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
Where it gives the different screen resolutions go with largest, if it calls for a file not present in your device just skip it and don't add extras. There are a lot of guides but that one I know works rather well, I've used it on 3 diff devices. Cooking custom recovery in kitchen works but not always correctly. By that I mean that you may not have the ability to backup or restore or install. You may not be able to control brightness or some other setting or it could be that usb does not work. It can be a combination of any of those things and more. It can also be that you never notice something not working because it does everything you want it to. Just letting you know what to expect and saying that building from source is always best, even when it's unavailable.

If you ever get the time can you port TWRP to the 100015685-E?

@rolenthedeep here is a WIP fstab. I have commented out the partitions that were not first_stage_mount If you try it as is to try to get an idea of which parts are needed for recovery there is no sd card in it as it too is commented out for now. Got caught up in some other issues and stopped looking at it for a while. Maybe it will help a little.

Any updates on this? I have the 10.1 3562 version

Database Users

welcome