Database Users

ZTE Open Firefox OS build thread (Mar25, updated for 3.0 build)

Hi,
I am new to Firefox OS, just got my ZTE Open last week. (used $10 from eBay)
I followed the instruction on the internet and XDA developers, compiled and flashed Firefox OS 2.1 into the ZTE Open.
Here is a link to the *.img files, feel free to play around with it.
https://drive.google.com/file/d/0B7HdrUmGwI8GRGlSZDdjMTBLMkk/edit?usp=sharing
2.1 seems running fine (so far so good), haven't seen it crashes since I flashed it this morning.
I can make phone call, surf the web, install new apps from the market, play mp3 and video files and the GPS is working.
It still has the same problems as the 1.3 build, the FM radio only works with speaker, the keyboard always display capital, recording video crashed the camera app after 2 seconds.
Here are the steps.
1. Update to official 1.1 release B06
2. Flash the 1.3 *.img built by linr76. (BTW, mine is a US version, but linr76's build is UK version, but it seems OK)
3. Flash my 2.1 *.img files. (pull the files from git on June 19, backup the system files from my phone on the 1.3 build)
BTW, I actually want to build 1.3 running BRANCH=1.3 VARIANT=user ./build.sh, but somehow the build script compiled 2.1 for me.

hevangel said:
2.1 seems running fine (so far so good), haven't seen it crashes since I flashed it this morning.
I can make phone call, surf the web, install new apps from the market, play mp3 and video files and the GPS is working.
It still has the same problems as the 1.3 build, the FM radio only works with speaker, the keyboard always display capital, recording video crashed the camera app after 2 seconds.
Click to expand...
Click to collapse
Thanks for the v2.1 compile! I flashed it to my Open today as well.
I noticed the same issues as you, as well as some new ones:
"Home" orb light doesn't work
Screen timeout doesn't work properly (10 seconds no matter what you set it to)
However, it is really awesome of you to get this compile out there for people to test and use
I'm trying (unsuccessfully) to get my 1.4 user to compile.

hevangel said:
Hi,
I am new to Firefox OS, just got my ZTE Open last week. (used $10 from eBay)
I followed the instruction on the internet and XDA developers, compiled and flashed Firefox OS 2.1 into the ZTE Open.
Here is a link to the *.img files, feel free to play around with it.
https://drive.google.com/file/d/0B7HdrUmGwI8GRGlSZDdjMTBLMkk/edit?usp=sharing
2.1 seems running fine (so far so good), haven't seen it crashes since I flashed it this morning.
I can make phone call, surf the web, install new apps from the market, play mp3 and video files and the GPS is working.
It still has the same problems as the 1.3 build, the FM radio only works with speaker, the keyboard always display capital, recording video crashed the camera app after 2 seconds.
Here are the steps.
1. Update to official 1.1 release B06
2. Flash the 1.3 *.img built by linr76. (BTW, mine is a US version, but linr76's build is UK version, but it seems OK)
3. Flash my 2.1 *.img files. (pull the files from git on June 19, backup the system files from my phone on the 1.3 build)
BTW, I actually want to build 1.3 running BRANCH=1.3 VARIANT=user ./build.sh, but somehow the build script compiled 2.1 for me.
Click to expand...
Click to collapse
BRANCH=v1.3 instead. And use VARIANT=userdebug would be better since it gets you more or less the same as eng build but not enabled by default (root acces, etc.).
Regarding the bugs you are mentionning, I have no issue on other devices with FM Radio app. Keyboard displaying capital is not a bug, it's a change from UX. Video recording crashing is a legit bug however.

lissyx said:
Keyboard displaying capital is not a bug, it's a change from UX.
Click to expand...
Click to collapse
That does not seem, to me, to be a change made for the better. The iOS keyboard has this same behavior, and it feels broken there as well.
What is the reasoning behind making the soft-keyboard case insensitive/static?
hevangel said:
BTW, I actually want to build 1.3 running BRANCH=1.3 VARIANT=user ./build.sh, but somehow the build script compiled 2.1 for me.
Click to expand...
Click to collapse
Hevangel, I issued my build with BRANCH=v1.4 VARIANT=userdebug ./build.sh and it build v2.1 for me as well.

Hevangel,
I was informed by gerard-majax on the #b2g IRC channel that the reason you and I got the v2.1 build was because we issued the commands wrong. You need to set the BRANCH and VARIANT during the ./config.sh stage, not at the ./build.sh stage like you and I did.
I have successfully compiled the BRANCH=v1.4 VARIANT=userdebug 2014-06-19(svn) FirefoxOS and flashed it to my Open.
I ran ./flash.sh gaia && ./flash.sh gecko over my v1.2(zte) install and then rebooted and cleared the cache partition. This gives me a working, but highly unstable Inari.
Working:
Prox/light sensor
Light orb on Home button
Everything else except known limitations (FM only over speaker)
Not Working:
All apps are unstable
b2g will crash randomly
Link to compiled images:
http://1drv.ms/Vp6rz4

Why it still says 13./1.4 Prerelease?

LinuxHolic said:
Why it still says 13./1.4 Prerelease?
Click to expand...
Click to collapse
What do you mean?
If you want to change branches to build v2.1, you'll need to do this.
$home\username\B2G
git pull
BRANCH=master VARIANT=userdebug ./config.sh inari
./repo sync

Saijin_Naib said:
What do you mean?
If you want to change branches to build v2.1, you'll need to do this.
$home\username\B2G
git pull
BRANCH=master VARIANT=userdebug ./config.sh inari
./repo sync
Click to expand...
Click to collapse
No i mean if i install 1.3 or 1.2 on my phone than why it still says 1.2/1.3 Prerelease in the Device Information?

LinuxHolic said:
No i mean if i install 1.3 or 1.2 on my phone than why it still says 1.2/1.3 Prerelease in the Device Information?
Click to expand...
Click to collapse
OH! Any image compiled by a non-official source/partner will always be tagged Pre-Release. Quality control thing, I think? Not sure.

Saijin_Naib said:
OH! Any image compiled by a non-official source/partner will always be tagged Pre-Release. Quality control thing, I think? Not sure.
Click to expand...
Click to collapse
I can't download your v2.0 and 2.1 builds from One Drive

Here you can find updated for 1.3 and 2.1 for ZTE Open images.
http://157.88.55.36:8080/job/master-inari/
http://157.88.55.36:8080/job/1.3-inari/
To update use these steps:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img

elav said:
Here you can find updated for 1.3 and 2.1 for ZTE Open images.
http://157.88.55.36:8080/job/master-inari/
http://157.88.55.36:8080/job/1.3-inari/
To update use these steps:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Please, which boot.img you used? And what partition for the ramdisk.img you has taken?

2.1 build and Keon??
Hello,
I have a ZTE Open and it's currently running Prerelease 1.3. I must say I'm quite happy with its performance and the bugs aren't crippling at all. I was thinking of upgrading to the 2.1 build from this thread. I was wondering though since I saw that there's a Geeksphone Keon 2.0 build. Since it looks exactly like a ZTE Open, the question popped into my head: "would that build work on a ZTE Open?". SO I turn that question over to the community here at XDADevelopers
Also, can I jump from 1.3 to 2.1? or would I have to do more of a 1.3 -> 1.4 -> 2.0 -> 2.1 sort of upgrade path?
Thanks!

TheEternalAbyss said:
Hello,
I have a ZTE Open and it's currently running Prerelease 1.3. I must say I'm quite happy with its performance and the bugs aren't crippling at all. I was thinking of upgrading to the 2.1 build from this thread. I was wondering though since I saw that there's a Geeksphone Keon 2.0 build. Since it looks exactly like a ZTE Open, the question popped into my head: "would that build work on a ZTE Open?". SO I turn that question over to the community here at XDADevelopers
Also, can I jump from 1.3 to 2.1? or would I have to do more of a 1.3 -> 1.4 -> 2.0 -> 2.1 sort of upgrade path?
Thanks!
Click to expand...
Click to collapse
No, Geeksphone Keon builds won't work on ZTE Open because both phones have different hardware
And yes you can directly jump from V1.3 to V2.1
Precompiled images by Saijin_Naib of ZTE Open

LinuxHolic said:
No, Geeksphone Keon builds won't work on ZTE Open because both phones have different hardware
And yes you can directly jump from V1.3 to V2.1
Precompiled images by Saijin_Naib of ZTE Open
Click to expand...
Click to collapse
Please see my thread here: ZTE Open (Inari) Build Versions & Issues for an overview of the various issues & limitations I've encountered on each SVN compile version using my ZTE Open.
If you want full hardware functionality, you're stuck with the official ZTE ROMs only. If missing GPS & home orb light don't bother you, then you can pick and choose the other versions at will.

Saijin_Naib said:
Please see my thread here: ZTE Open (Inari) Build Versions & Issues for an overview of the various issues & limitations I've encountered on each SVN compile version using my ZTE Open.
If you want full hardware functionality, you're stuck with the official ZTE ROMs only. If missing GPS & home orb light don't bother you, then you can pick and choose the other versions at will.
Click to expand...
Click to collapse
I'll definitely check them out. I don't use gps on my ZTE Open, so that is a non issue for me. In my 1.3 pre-release the home light works just fine. I don't think it would bother me much really. I'll just have to see. I may just wait for some new phones to come out before spending time on my poor broken ZTE Open lol
Thank you though for the info.

TheEternalAbyss said:
I'll definitely check them out. I don't use gps on my ZTE Open, so that is a non issue for me. In my 1.3 pre-release the home light works just fine. I don't think it would bother me much really. I'll just have to see. I may just wait for some new phones to come out before spending time on my poor broken ZTE Open lol
Thank you though for the info.
Click to expand...
Click to collapse
No problem.
So far in my testing, v1.4 seems to be the most recent SVN that will have a working Home Orb light, but it was also far and away the most unstable version I have tested yet (surprisingly).

Flash steps
TheEternalAbyss said:
I'll definitely check them out. I don't use gps on my ZTE Open, so that is a non issue for me. In my 1.3 pre-release the home light works just fine. I don't think it would bother me much really. I'll just have to see. I may just wait for some new phones to come out before spending time on my poor broken ZTE Open lol
Thank you though for the info.
Click to expand...
Click to collapse
Hi!! Thank you very much for the information and the images, it really helps when you try to compile the source from a computer that is not debian 64...
I am in the way of flashing my ZTE open to 2.0 and i found in the Precompiled images by Saijin_Naib there is only a ramdisk,userdata and system images, ¿which are the correct steps to get the update? do i need any other boot.img or recovery.img that is not present in the repository?
BTW, i have tried to do just fastboot flash boot ramdisk.img as @elav said below but i get an error: FAILED (remote: image is not a boot image)
Thanks!!

LinuxHolic said:
No, Geeksphone Keon builds won't work on ZTE Open because both phones have different hardware
And yes you can directly jump from V1.3 to V2.1
Precompiled images by Saijin_Naib of ZTE Open
Click to expand...
Click to collapse
Hi!! Thank you very much for the information and the images, it really helps when you try to compile the source from a computer that is not debian 64...
I am in the way of flashing my ZTE open to 2.0 and i found in the Precompiled images by Saijin_Naib there is only a ramdisk,userdata and system images, ¿which are the correct steps to get the update? do i need any other boot.img or recovery.img that is not present in the repository?
BTW, i have tried to do just fastboot flash boot ramdisk.img as @elav said below but i get an error: FAILED (remote: image is not a boot image)
Thanks!!

mahdsip said:
Hi!! Thank you very much for the information and the images, it really helps when you try to compile the source from a computer that is not debian 64...
I am in the way of flashing my ZTE open to 2.0 and i found in the Precompiled images by Saijin_Naib there is only a ramdisk,userdata and system images, ¿which are the correct steps to get the update? do i need any other boot.img or recovery.img that is not present in the repository?
BTW, i have tried to do just fastboot flash boot ramdisk.img as @elav said below but i get an error: FAILED (remote: image is not a boot image)
Thanks!!
Click to expand...
Click to collapse
Connect your phone in USB Debugging Mode and enter the following commands:
adb reboot-bootloader
fastboot erase userdata
fastboot erase cache
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache ramdisk.img
And you're good to go

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

fire hd 8 bootloop after installing custom rom

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

Bricked onn 10.1 with keyboard

So I bought one of those onn tablets from Walmart, went to flash phussons quack gsi for Q and whilst the system flashed fine via fastboot it refuses to actually boot (bootloop on the onn screen) I can't get into recovery either. Fastboot -w fails because it can't create an image for the userdata partition (when I go to manually format userdata it says the partition table doesn't exist.) I'm able to flash to the boot, recovery and system partitions no issue.

Android 10 roms I have tried do not work... I have the onn 8 and on 10 w/o keyboard.
Also I had no issues flashing android 9 roms on the 8 but on the 10 all roms have issues with no sound from the speakers but sound through wired & bluetooth headsets some roms have graphical issues some have bluetooth... but all seem to have sound problems... and some will not boot past boot animation.
Roms I got too boot were phh's 9, beast rom, bootleggers, bliss and liquid remix. Liquid remix runs the best so far... but on the 8 not the 10

I also tried the /e/ os gsi Wich is based on pie that didn't boot either, I'll try liquid remix
went to format system before flashing and heres the output i got
Invalid erase-block-size 0: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-wirxYd: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for system
same type of error i was talking about with my userdata partition

What was your method for flashing?

Unlocked the bootloader with fastboot flashing unlock
Fastboot -u flash system /name/and/location/of/gsi
I had erased my system partitions before i flashed the gsi the first time and I think that's where I screwed up
If I could get into the recovery I'd just adb sideload the ota and start again

Be careful you don't lose your battery charge, it doesn't charge in fastboot, so it can be easy to get into a difficult situation with a battery below 30%
I can get you stock system, boot and recovery images for your model later this evening.

NFSP G35 said:
Be careful you don't lose your battery charge, it doesn't charge in fastboot, so it can be easy to get into a difficult situation with a battery below 30%
I can get you stock system, boot and recovery images for your model later this evening.
Click to expand...
Click to collapse
Alright, thank you and I've already been attempting to use your back up images of stock off xda to try and restore it is there anything special I need to do or are you going to get like a flashall file made?

I am going to get the system and vendor partitions from the ONA19TB007 uploaded (currently only have boot and recovery)
Once those are up, you should be able to flash them via fastboot.

NFSP G35 said:
I am going to get the system and vendor partitions from the ONA19TB007 uploaded (currently only have boot and recovery)
Once those are up, you should be able to flash them via fastboot.
Click to expand...
Click to collapse
Hey, any updates it's been a few hours and I'd love to get the tablet fixed tonight

kanaan360 said:
Hey, any updates it's been a few hours and I'd love to get the tablet fixed tonight
Click to expand...
Click to collapse
Hey, really sorry about that. An emergency came up yesterday.
I'll get that uploaded whenever I can. Sorry again.

NFSP G35 said:
Hey, really sorry about that. An emergency came up yesterday.
I'll get that uploaded whenever I can. Sorry again.
Click to expand...
Click to collapse
You're good man, thanks so much again.

Images from the The May update are here (still waiting on the system image to finish uploading)
https://www.androidfilehost.com/?w=files&flid=301680

NFSP G35 said:
Images from the The May update are here (still waiting on the system image to finish uploading)
https://www.androidfilehost.com/?w=files&flid=301680
Click to expand...
Click to collapse
Awesome thanks, any word on the system image?

kanaan360 said:
Awesome thanks, any word on the system image?
Click to expand...
Click to collapse
I don't know if it's AFH or my internet connection... It's been uploading over 24hrs now... I'm stymied.
89% complete though. Sorry it's taking so long

Finally finished uploading!
https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227

NFSP G35 said:
I don't know if it's AFH or my internet connection... It's been uploading over 24hrs now... I'm stymied.
89% complete though. Sorry it's taking so long
Click to expand...
Click to collapse
The speed is by server. Quebec seems to be fast for me most the time. If there is It's there decryption on twrp? I have been happy with stock personally but if you need any more images let me know. Also let me what way you want them. I can flash then use twrp or use dd commands but I would need to know what dd you wanted. I don't have sptools installed right now though. I could probably get it working on my Mac os if needed be though since I have many of the Linux libraries/services. Last option would take the longest since it's actually learning new cli commands. I am kind of a slacker but if someone has a bricked device then... I want to help.

Vortell said:
The speed is by server. Quebec seems to be fast for me most the time. If there is It's there decryption on twrp? I have been happy with stock personally but if you need any more images let me know. Also let me what way you want them. I can flash then use twrp or use dd commands but I would need to know what dd you wanted. I don't have sptools installed right now though. I could probably get it working on my Mac os if needed be though since I have many of the Linux libraries/services. Last option would take the longest since it's actually learning new cli commands. I am kind of a slacker but if someone has a bricked device then... I want to help.
Click to expand...
Click to collapse
Thanks, but the files finally finished uploading in the small hours last night.
I figured out its my stupid internet connection at home... apparently, while my download speed is great, my upload speed could be outpaced by a burro carrying floppy disks
Took my laptop to work and everything has been uploading much faster.
@kanaan360, I have images for you at:
https://www.androidfilehost.com/?w=files&flid=301679 or https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
The May images are up, October ones will be there in a few minutes.

NFSP G35 said:
Be careful you don't lose your battery charge, it doesn't charge in fastboot, so it can be easy to get into a difficult situation with a battery below 30%
I can get you stock system, boot and recovery images for your model later this evening.
Click to expand...
Click to collapse
so i ran into that situation what do i do. is it bricked beyond repair?

nevor70168 said:
so i ran into that situation what do i do. is it bricked beyond repair?
Click to expand...
Click to collapse
Not hard bricked by a long shot.
Several of us have recovered from this scenario.
Somewhere around here I posted a link to a xda thread with a similar situation that can happen with some HTC phones. Basically, you build a script to constantly reboot it into fastboot.

NFSP G35 said:
Not hard bricked by a long shot.
Several of us have recovered from this scenario.
Somewhere around here I posted a link to a xda thread with a similar situation that can happen with some HTC phones. Basically, you build a script to constantly reboot it into fastboot.
Click to expand...
Click to collapse
everytime i try to boot into fastboot mode it reboots it doesnt go into fastboot mode, is this because the battery life is low and does not want to boot into fastboot mode? Also how would i charge my device it keeps flashing on the low battery icon. any help would be appreciated also a link to your post would help me greatly.