Related
Hello everyone, I have another approach to the bootloader, but I don't have any experience with kexec or that much free time in my possession. As you probably already know, we can already run whatever we want on the D855 given that we run fastboot on a computer on every restart, what if we implement kexec in a way that it reloads the kernel currently running and restarts the GUI? It's possible to run a custom recovery this way, and with xposed, we can even hook to the system dialogs and silently run kexec when the user hits reboot/reboot to recovery. What do you guys think about it? It is certainly not an unlock since if the battery goes dry or you need to shut down you still need a computer but I think it's a great start! If anyone is interested in helping, feel free to reply!
CBKarabudak said:
Hello everyone, I have another approach to the bootloader, but I don't have any experience with kexec or that much free time in my possession. As you probably already know, we can already run whatever we want on the D855 given that we run fastboot on a computer on every restart, what if we implement kexec in a way that it reloads the kernel currently running and restarts the GUI? It's possible to run a custom recovery this way, and with xposed, we can even hook to the system dialogs and silently run kexec when the user hits reboot/reboot to recovery. What do you guys think about it? It is certainly not an unlock since if the battery goes dry or you need to shut down you still need a computer but I think it's a great start! If anyone is interested in helping, feel free to reply!
Click to expand...
Click to collapse
I made some research about kexec and, since the host kernel doesn't support kexec we cannot use it. The only solution will be to build a module but its hardest then it appears.
Building a kexec module isn't that hard. It does however require certain symbols to be exported from the zimage to work. I've only had my G3 for a few days so not had time to check
AngelBob said:
Building a kexec module isn't that hard. It does however require certain symbols to be exported from the zimage to work. I've only had my G3 for a few days so not had time to check
Click to expand...
Click to collapse
Waiting for you then! Hope you will have soon some free time!:good:
Hi,
I have some free time and would like to join a group of Ubuntu Touch devs. Is this a good place to ask or should I re-post on Canonical?
You can attempt to re-post on Canonical's forums, but the Ubuntu Touch Google+ Community is pretty active with both developers that work on Ubuntu Touch and consumers. I know I've seen Canonical's Michael Hall post in there as well as a couple others at some points.
https://ubports.com
This might be the place for you. They are asking for devs.
Good luck. I hope you start with the shamu (Nexus 6)
kidhudi said:
https://ubports.com
This might be the place for you. They are asking for devs.
Good luck. I hope you start with the shamu (Nexus 6)
Click to expand...
Click to collapse
I have a Nexus 5 and I want to dual boot Ubuntu with Android. There are 2 instructions on ubports.com but the one using MultiROM(to dual boot) has no link! I followed other guides with MultiROM but Ubuntu won't boot. Android's still working fine, though.
Matrixians 14 said:
I have a Nexus 5 and I want to dual boot Ubuntu with Android. There are 2 instructions on ubports.com but the one using MultiROM(to dual boot) has no link! I followed other guides with MultiROM but Ubuntu won't boot. Android's still working fine, though.
Click to expand...
Click to collapse
You will likely need to look into the official Ubuntu Dualboot solution and adapt that for the hammerhead. Ubports ROMs are intended to be installed via the ubuntu-device-flash commands only and are likely not supported under MultiROM easily.
That said, if you have an UBports system image installed via MultiROM, and it appears via multirom, you can always check /proc/last_kmsg after a failed Ubuntu Boot (while in multirom's boot manager) to see where the boot went bad, you could also open the ROM under MultiROM's recovery and hit Patch init and see if that helps.
Other than that, I'm afraid the only supported installation method for the community ports are the instructions listed on the page. You may also have some luck looking for KDE Plasma Mobile tutorials (which use a standard Ubuntu Touch image for their basic installation, not sure if they do the same thing as ubuntu-device-flash though).
One last thought, have you tried MultiROM manager? It may have images for your system (I recommend going no further than rc-proposed, devel does not run many apps from the Store and is based off Xenial, sp there's some library incompatibilities with apps installed from the Ubuntu Store. Devel branches are also not guaranteed to boot, however rc-proposed and stable should at least boot for you unless their builds are fundamentally broken, in which case, you should bring it up with the maintainer)
Thanks, but now Ubuntu Touch worked. I installed the dual boot app and added the channels for hammerhead. But now Everytime I boot into Ubuntu it removes my custom recovery. Instead of booting into the recovery, it boots into Ubuntu Touch, and it only happens if I reboot into Ubuntu Touch, so I basically have to reinstall recovery after using Ubuntu, which is very inconvenient.
Matrixians 14 said:
Thanks, but now Ubuntu Touch worked. I installed the dual boot app and added the channels for hammerhead. But now Everytime I boot into Ubuntu it removes my custom recovery. Instead of booting into the recovery, it boots into Ubuntu Touch, and it only happens if I reboot into Ubuntu Touch, so I basically have to reinstall recovery after using Ubuntu, which is very inconvenient.
Click to expand...
Click to collapse
I replied on the G+ page too, but figured I'd post here as well so others may benefit if I'm right here. -SNIP-
Edit: I just realized how the dualboot utility works.. It is likely the application overwriting your recovery image. If you want to keep MultiROM, I'm afraid you'll need to reinstall Ubuntu with MultiROM manager as the dualboot utility writes Ubuntu's boot.img to the recovery partition to boot Ubuntu.
Yeah, thanks, but it only works with the dual boot utility. I have my issues with MultiROM if you've read the first post on G+. But now I restored my system to a previous state when there was no dual boot utility so I don't want Ubuntu Touch anymore. Linux Deploy would do the trick, but now even IT has problems installing trusty. After the installation, I reconfigured it from the Linux Deploy menu and when I start it, it failed to start the VNC server and I don't know why. Is it the architecture of Trusty that i chose?
I did see your post, my apologies that MultiROM isn't booting for you, I ran into this weird issue myself on the Flo, normally it can be solved from trying other revision numbers in either the stable or rc-proposed channel. Sadly, through the Dualboot installer, there's no way around this (bar writing an /etc/init.d script for Android that automatically flashes the TWRP image when Android boots back up)
It may very well be the architecture of trusty. I would recommend trying vivid, saucy, wily or xenial. (any of the more recent versions, trusty is rather old at this point and you would've been getting Vivid [15.04] via Ubuntu Touch)
That said, you'll get much more performance using XServer XSDL from the Play Store and setting Linux Deploy to use it (X Server -> Use XServer XSDL), it also allows you to use any X application remotely or locally (on a remote machine you'd do export DISPLAY=[Tablet IP]:0)
As for Ubuntu Touch, if you go back through and attempt MultiROM again, start with the latest revision (I recommend staying far away from devel and devel-proposed unless you are purposely wanting to develop applications for Xenial, most applications targeting Vivid here don't work.) and then if the latest fails to boot, try the next one down the line. Another issue here could be a kernel that doesn't properly support KEXEC, have you tried MultiROM with a different KEXEC compatible kernel? I honestly can only recommend two different configurations, the singluar installation (Ubuntu being the only OS, gives you the most storage space) or MultiROM :\ I don't have much experience with the Dualboot app.
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
Here's a good one for you:
So, I decided I wanted to try for a more permissive kernel, so I decided to flash new firmware to my T510 and get the latest Nexus ROM version from @Magendanz. The last time I had Nexus, the Nethunter chroot that I also install granted me y-cable support. I wanted that back (I'm going to try my hand at kernel building next). Anyway, I flashed the BUA1 firmware through Heimdall (I linux), and due to my past successes, I proceeded to flash the matching TWRP and OS in quick succession. I was somewhat concerned upon completion about the very long hangup on the Google loading screen during bootup (hours). So, I got impatient and decided to try again. I was unable to get Heimdall to initialize, and while rebooting I missed the key-combo for recovery and ended up successfully booting the Nexus ROM. So, now I'm running TWRP and NEXUS ROM (both BUA1) on a machine with BTH4 firmware (verified via multiple sources).
So, I guess my question is: Should I be concerned? Do I have a magic tablet? Can I monetize this power? But, really, has anyone else had this happen with bricking a device? Is there any good reason to leave it as is? Should I start fresh from firmware? Do you know of a kernel that'll flash to my T510 that will run an external wifi adapter?
Thanks for the advice.
Hi,
Since I use Linux I'm only left with the good ol' ADB and fastboot.
I know the questions are basic, but I'm rooting a phone once or twice a year, so I better be safe than sorry...
# Device:
j7y17lte
# Model
SM-J730F
# CPU Architecture
armv8l
# Android Version
7.0
Questions:
1. Which recovery to use for my phone? This one https://eu.dl.twrp.me/j7elte/ ? And how to install it via ADB????
2. What is the best procedure to root it? SuperSu, Magisk, Box?
3. I'm not into updating to latest versions of Android since 7 works for me just well. I'm more into removing bloatware and Google as much as possible. What is your opinion on that front? And also, if there is some super cute custom ROM which has Android version 8 or 9 or 10, do I just install it normally? If I remember upgrade will work , but downgrade is a bit tricky...?
4. And finally , which custom ROM do you recommend?
I know it's a lot to ask but even one answer will help me out a lot.
Thanks
You cannot go without download mode, but you can use Heimdall( just similar to Odin but for Linux)
[PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available)
What is Heimdall? Heimdall is a cross-platform open-source tool suite used to flash ROMs onto Samsung Galaxy S devices. How does it work? Heimdall uses the same protocol as Odin to interact with a device in download mode. USB communication in...
forum.xda-developers.com
If you only needs debloat, (no you cannot install microG via this method)
How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com
will be fine but as a disclaimer android 7 is super old, and I do not hold any responsibility if you faces any problem using android 7.
I just now saw that I didn't thank you. Pardon me.
Heimdall gave no result, so I guess I'll have to do it over windows PC that I got my hands on these days.
Thanks anyhow. I didn't know about that project.