Newly build rom stuck at bootlogo. - Android Software Development

Im trying to build cm13 unofficial from source i downloaded and im following this guide: http://xda-university.com/as-a-devel...id-from-source
And i used this guide to get source code and some others downloaded: https://nathanpfry.com/how-to-setup-...-android-roms/
Im using openjdk 8.
I got it to compile and it said "done" but when i flash the rom.zip it gets stuck at manufactor logo. i did not install anything else. thats all. ideas?
Phone is Nexus 4 8GB MAKO.

Bump

You're going to need to get some sort of logs to troubleshoot such as dmesg or kmsg. Unfortunately in order to get that without being able to boot the rom and enable root/developer mode settings, I believe you will need a modified kernel.
Sent from my SM-T350 using Tapatalk

Koognod said:
You're going to need to get some sort of logs to troubleshoot such as dmesg or kmsg. Unfortunately in order to get that without being able to boot the rom and enable root/developer mode settings, I believe you will need a modified kernel.
Sent from my SM-T350 using Tapatalk
Click to expand...
Click to collapse
Ideas where to find that?

You'd have to either make one yourself or find a developer who will do it for you. sorry I cannot help you more than that. here are a few more pages I found when googling https://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging , http://bootloader.wikidot.com/linux:android:kmsg

could possibly be a reference
https://github.com/ResurrectionRemix/android_frameworks_base/issues/139

Related

Verizon SCH-i815 unbricking help / need a kernel w. aroma

Hi,
I had edited my build.prop and it bricked my pad. I was told to look for a kernel with aroma file manager. Unfortunately, I can't seem to find one that's for the Verizon SCH-i815 version. I would chalk it up to my inexperience, so i was hoping someone could help me.
Just to be clear, I'm not looking to have a custom rom on my pad, I just want to get it back operational. I have odin on my pad itself, so i'm just looking to flash a tar, then use CWM to fix my build prop by restoring the original version.
Were you running ICS or Honeycomb? Either way, it seems that if you can get into download mode you can flash recovery with Odin and then a stock ROM. You might check the i815 summary thread:
http://forum.xda-developers.com/showthread.php?t=1760587
Or the i815 ICS thread:
http://forum.xda-developers.com/showthread.php?t=1932597
Thanks for the links, i'll read up and see if that solves the problem. I was running the stock honeycomb as verizon hadn't yet updated the tablet yet, though they are supposed to soon.
Kralik said:
Were you running ICS or Honeycomb? Either way, it seems that if you can get into download mode you can flash recovery with Odin and then a stock ROM. You might check the i815 summary thread:
http://forum.xda-developers.com/showthread.php?t=1760587
Or the i815 ICS thread:
http://forum.xda-developers.com/showthread.php?t=1932597
Click to expand...
Click to collapse
okay, so i have honey comb on the device, and i'm fine with that honestly, i looked through the first thread, but did not see anything there that mentioned aroma (which I was told to look for since i can't boot beyond Odin). Do you have any recommendations both for a file to download and a method?
Basically, my pad will charge and you get some sort of "response" when you power it on and plug it into a pc. I can enter odin mode by pressing power and volume button, but that's it. I'm just trying to get it back, i don't really care if i have to wipe all the data on there or not, but obviously it would be cool if i did. The way this happened to me was that i edited the model name in the build.prop file after seeing some tutorials on it. There are obviously a ton of tutorials on this, but i've tried several to no avail.
Perhaps someone with more expertise can step up, but I'm pretty sure that if you flash a rom it overrides your build.prop?
All you did was change the build.prop, right? If you can connect with adb, I'm thinking you can probably copy over a build.prop to replace yours.
Sent from my SCH-I815 using xda premium
yes, that's all i did. I don't have any experience with ADB, though i'm not scared of command line ... just have never used it at all. In looking at something like this: http://tabletmods.blogspot.com/2012/06/modifying-buildprop-in-pc.html my concern would be that there's no way for me to put it into debugging mode. Any thoughts on that would be appreciated
helpermonkey said:
yes, that's all i did. I don't have any experience with ADB, though i'm not scared of command line ... just have never used it at all. In looking at something like this: http://tabletmods.blogspot.com/2012/06/modifying-buildprop-in-pc.html my concern would be that there's no way for me to put it into debugging mode. Any thoughts on that would be appreciated
Click to expand...
Click to collapse
Did you try? Maybe it is in debug mode? Would you find your build.prop.backup with ADB commands?
However, if you do things you do, you need to have a backup
So flash another kernel and you will have a cwm. Not sure but I think in cwm you should have an option to activate usb-debugging...
md p9516 - root -waiting for cwm -- thnx2all
Hi there,
I have only had a little bit of time to address this over the past few weeks but i'm hitting brick walls everywhere I turn. At this point, I just want to restore my tablet to stock. I am not entirely sure why this is so incredibly difficult, but I cannot find a method that seems to allow me to replace my backed up build.prop. So meanwhile, I helped a friend out with a bricked nexus 7 using the nexus root toolkit, is there anything like this for the galaxy tab?
To clarify:
I had a rooted galaxy tab running 3.2 from Verizon. I edited the build.prop and it ended up bricking my tablet. The only option is to boot into recovery, at which point I'm presented with volume up (continue) or volume down (cancel). If i hit up, i'm taken to ODIN MOode, where the product name is listed along with binary (samsung official) and custon binary download: no. That's all i can do.
I downloaded CWM recovery from here: http://forum.xda-developers.com/showthread.php?t=1542897 and followed the instructions here: http://theunlockr.com/2012/11/14/how-to-install-clockworkmod-recovery-on-the-samsung-galaxy-tab-7-7/
however, when i subsequently try and boot into recovery mode, i have no luck. It does not seem to "take" the update thus i'm left with odin mode on the tablet.
!
i think - wrong area to ask...

i have taken the lg g2 rom port to nexus 4

I am stuck after porting the LG G 2 ROM into Nexus 4everything goes fine till I go to boot where I get stuck at the Google logo install fine but then upon reboot get stuck at the Google logo I have taken in copied over the three lib files as suggested in mini tutorialany help would be greatly appreciated
streetmedic said:
I am stuck after porting the LG G 2 ROM into Nexus 4everything goes fine till I go to boot where I get stuck at the Google logo install fine but then upon reboot get stuck at the Google logo I have taken in copied over the three lib files as suggested in mini tutorialany help would be greatly appreciated
Click to expand...
Click to collapse
You do know that porting a ROM involves much more than following an "Easy port" tutorial, don't you? Drivers, kernels, framework, libs etc. have to be ported too.
Does adb work? If yes, try getting a logcat.
abaaaabbbb63 said:
You do know that porting a ROM involves much more than following an "Easy port" tutorial, don't you? Drivers, kernels, framework, libs etc. have to be ported too.
Does adb work? If yes, try getting a logcat.
Click to expand...
Click to collapse
Yes I'll grab that and yes I'm aware that I'll need to do some modding of files . I'll post those in a bit once kids are off my computer. Both bases I used are 4.22 and are both made for T-Mobile. I let you know.
I am keeping eye on this thread. Thanks.
Sent from my Nexus 4 using Tapatalk
I tried to get a log but if I am correct it won't log due to its a fresh install and it does not boot past Google logo. If I am mistaken please show me where I have gone wrong. Help is most welcome and always appreciated.
streetmedic said:
I tried to get a log but if I am correct it won't log due to its a fresh install and it does not boot past Google logo. If I am mistaken please show me where I have gone wrong. Help is most welcome and always appreciated.
Click to expand...
Click to collapse
you will need drivers for it to boot, among other things. most likely you would will have to write your own, since they are closed source. its not as easy as just making the rom fit the n4, its everything else that goes with it that makes it hard.
I can help you maybe
Add me on skype i can help you maybe skype:vova50006:good:

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

Categories

Resources