Hello,
I was wondering how I could change the bootloader static image (the very first image you see when you turn it on says stuff like seandroid enforcing and stuff).
I searched and saw that it was done for the epic 4g but from the thread it looked like it was specific to that device.
cm0002 said:
Hello,
I was wondering how I could change the bootloader static image (the very first image you see when you turn it on says stuff like seandroid enforcing and stuff).
I searched and saw that it was done for the epic 4g but from the thread it looked like it was specific to that device.
Click to expand...
Click to collapse
It's built into the kernel and would need to be changed in the kernel. I don't think it is even possible with stock.
Sent from my SM-G900T using Tapatalk
tp2215 said:
It's built into the kernel and would need to be changed in the kernel. I don't think it is even possible with stock.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Ok so what your saying is that in theory anyways I would have to get the source of a kernel change the image and compile it from scratch? You also said it most likely would not be possible with stock, stock kernel you mean,? Because I thought custom kernels were already out.
Yea, you would need to decompile the kernel and replace the image.
Sent from my SM-G900T using Tapatalk
tp2215 said:
Yea, you would need to decompile the kernel and replace the image.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Ok I got an idea now, but I am surprised that it is in the kernel because the android boot sequence goes bootloader then kernel then android and I thought the picture of anything would be in the bootloader, but I will defently get a hold of a custom kernel and poke around thanks for the info
Ok I'm at a loss at the moment after digging around in the blaze kernel source I failed to find any logo picture at all and after further research expanding to previous galaxy s models and other Samsung lines I determined one common denominator, param.lfs.
Now I ran a command to determine the partitions along with their familiars (I don't remember the command at the moment) and it came back with mmcblk0p11 with familiar "param" so I am guessing this is the one.
I then ran command
Dd if=/dev/block/mmcblk0p11 of=/storage/extSdCard/wkinglfs/param.lfs which outputted a 10mb file however when I open it in a hex editor it's all 0's
At this point I try to mount it in the file system by first creating folder ".lfs" in /mnt/ and then running mount -o remount,rw /dev/block/mmcblk0p11 /mnt/.lfs which outputs the error "mount: invalid argument.
I am stuck here, I am not really sure where to go from here
Oh I almost forgot I was going to attach a screenshot and some reference links.
A guide for the Samsung fascinate
http://forum.xda-developers.com/showthread.php?t=1279289
A guide for the Samsung galaxy s2
http://forum.gsmhosting.com/vbb/8591568-post36.html
A guide for Samsung galaxy tab 2
http://forum.xda-developers.com/showthread.php?t=1898377
And finally some instructions for HTC sensation
http://forum.xda-developers.com/showthread.php?t=1442872
Still stuck...
No matter how I dump or where I dump param partition the file I dump always comes out full of zeros in the hex editor and I am confident that this is the area I need to modify to obtain my goal, any help is greatly appreciated.
Partial success, after going through the aboot dump with a hex editor and copying out from FFD8 to FFD9 into a new jpeg file I was able to get many images out of it, most importantly the boot splash images, and then reinserting my custom images I flashed using dd if=/storage/extSdCard/abootnew.mbn of=/dev/block/mmcblk0p6 however upon reboot I still see Samsung logos, any help would appreciated
Ok so I redumped aboot to see why itwas still displaying Samsung logos and come to find out the new one never got flashed in the first place so the dd command referenced earlier did not work so I tried flashing using heimdall but apparently heimdall does not work yet for the galaxy s5.
How do I package aboot for use with odin or is there another way to flash aboot?
Related
Ok, as many of you know, the only thing between custom ROMs and your phone is the fact that we can not get the ROMs that we make to flash correctly in our current CWM recovery. We either get status 0, status 1, status 6, or status 7 errors when flashing. Most of these errors directly correlate with the boot.img command line(s) in the updater script.
uoY_redruM and I have spent over ten hours a piece trying to figure this out and have made progress but are still stuck.
We soon found out that the kitchens we were using to cook our ROMs did not have the latest directory for our phones partitions and their addressess (mmcblk0p1, etc.) This directed us to where we need to look to fix this.
The critical partitions we need to make ROMs flash are
1. Data
2. System
3. Boot
4. Cache
5. (optional) SDCard
It was easy enough to find 1,2, & 4, however the boot was a little bit trickier.
There are drives on our phone that had the following IDs:
1. mmcblk0p5 aboot
2. mmcblk0p7 boot
3. mmcblk0boot1 disk
4. mmcblk0boot0 disk
We believe that the real boot partition is 7, however we have yet to get a fully functional ROM up and running, despite writing the boot.img to p7.
With certain modifications to the boot.img lines in the updater script, I have been able to flash a ROM, but upon boot I lose SU permissions and the radio is borked (does not detect SIM card). Clearly this is still not functional and is caused by the boot.img (kernel) not being included in the ROM.
Attached is a scanned copy of a list of all of the partitions in our phone, along with their ID.
This is a thread where we can easily bounce ideas off of each other and hopefully get to the root of this problem ASAP.
Let's please keep this on topic. Thanks.
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Reviewers said:
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Click to expand...
Click to collapse
Yeah, we're starting to think it's recovery related.
We've (well most he) got the ROM to boot up now....but......and that's a big but.....it reads as if we have no SIM card. So, that's where we're currently stuck.
Same place boots loads kernel but no root or radio same sim card error
Wildchld said:
Same place boots loads kernel but no root or radio same sim card error
Click to expand...
Click to collapse
Are you using an insecure boot.img?
FiveOhFox said:
Are you using an insecure boot.img?
Click to expand...
Click to collapse
yep
Built in the kitchen
---------- Post added at 06:46 PM ---------- Previous post was at 06:41 PM ----------
I think it maybe the recovery too because I have lost root on restores
Wildchld said:
yep
Built in the kitchen
Click to expand...
Click to collapse
Ok. I'm trying it with secure boot.img files to see if that has any bearing on our results but so far nothing.
Ok well I'm going to shelf working on the script for a while and instead start working on my ROM and possibly learning how to make a recovery lol.
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Reviewers said:
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Click to expand...
Click to collapse
Why are you so adamant that it's the recovery?? You don't even own the phone!
I owned the amaze before and it didn't flash with 1 recovery but it worked on another.
I know this is Samsung but another user is agreeing with me as well.
Read the thread I made in General.
Flashing something from another phone will never work 100% as made for that phone.
---------- Post added at 01:24 AM ---------- Previous post was at 01:23 AM ----------
Plus when I get the phone I'll look into it as well.
I might not be much help in this area but I'll do what I can.
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
uoY_redruM said:
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
Click to expand...
Click to collapse
If you use the update-binary from the EU rom the status 6 error goes away but same results but the kernel will load. Status 6 error is a syntex error not because of the script but the binary is looking for different parameters.
Also I see no Sprint roms being dev maybe they have the same problem
One last shot before work... Attached is a working script and binary
Rom boots fine and about shows baseline unknown so maybe we need to load the radio in the rom also.
Also when I restore a nandroid radio comes back but won't connect till I turn off wifi then service returns.
Here's the thing I found odd....
If you use CWM to pull a backup, the boot.img/recovery.img are both 10MB in size.
If you use the Toolkit to pull a backup, the boot.img/recovery.img are 2MB/512KB.
Why is that? That doesn't make any sense to me. They should be duplicate but they're not.
....the only thing that comes to mind is maybe the Toolkit (since it was designed for the international phone) points to different partition points and aren't pulling the correct files? Then again, why would they be named properly?
That's where I'm at for today.
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
uoY_redruM said:
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
Click to expand...
Click to collapse
You used the recovery.img from what, again? And the script posted above writes to p18 which is recovery so that's not a problem.
So it boots but is missing radio? Do you have root?
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
uoY_redruM said:
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Click to expand...
Click to collapse
Lol your right but i have loaded this nandroid like 30 times i know its good
Sent from my SGH-T999 using Tapatalk 2
FiveOhFox said:
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
Click to expand...
Click to collapse
Found a few more files that could be of use. Five is writing up some commands to try flashing them.
I'm starting to feel really good about today!
Hi all,
I've got a VZW G Tab 2 7.0 Got it rooted and now looking to port CWM over to it.
I found This guide to port cwm, however he states it won't work for Samsung devices. I also attempted using the Recovery Builder with no luck. It wouldn't boot into CWM at all.
My question is.. can somebody give me some tips on how to port CWM to my tab? I've got some experience with programming/scripting/linux, but no idea where to start!
Thanks in advance
That guide is old, so it should work for Samsung devices now. Back in the days of the original SGS phones, it didn't due to a different recovery/kernel setup. If you can pull the boot.img and recovery.img from the tablet, it should be relatively easy to get it to work. Seeing as people have rooted the I705, that should be easy enough to do.
Ah ok that's good to know. I have already pulled all of the stock partitions for my own keepsake. I'll do what I can. Thanks man.
Well I followed the guide to exactly and got a recovery.img.. same result as I had using the 'builder'. The device reboots, little blue words saying 'recovery booting'. Screen goes black, then lights up with black background, flashes once, then reboots normally.
recovery.fstab has the correct values for this tab.
Code:
/boot emmc /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p14
/data ext4 /dev/block/mmcblk0p15 length=-16384
/cache ext4 /dev/block/mmcblk0p17
/recovery emmc /dev/block/mmcblk0p18
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/efs ext4 /dev/block/mmcblk0p11
/modem emmc /dev/block/mmcblk0p1
Would a locked bootloader prevent a CWM from booting? How would I tell if it is? In 'download mode', in the top left corner it says the following:
ODIN MODE
PRODUCT NAME: SCH-I705
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: Enabled
Then in the middle of the screen it says 'Downloading.. do not turn off...'
Don't know if this means the BL is locked or not, though.
My recovery.img download
If anyone want's me to post any more info let me know.
EDIT: What else needs to be done to build a successful recovery? I hardly think it's as easy as it is in the guide.. though I could be wrong.
http://forum.xda-developers.com/showpost.php?p=31671148&postcount=21 No feedback? Fail?
ketut.kumajaya said:
http://forum.xda-developers.com/showpost.php?p=31671148&postcount=21 No feedback? Fail?
Click to expand...
Click to collapse
Didn't notice that! I stopped following since It seemed the others did as well. Yes... fail. I'll check that out.
I'd like to know more about the process, though. So my questions still stand
I have my own scripts to unpack and repack boot.img or recovery.img using unpackbootimg and mkbootfs tools. What I've done:
1. Unpack yours stock recovery
2. Add CWM's /res/keys contents to yours recovery /res/keys
3. Repack the recovery
Code:
$ unpackbootimg.sh recovery.img
Edit /res/keys
Code:
$ repackbootimg.sh recovery.img
I'm getting the same reboot issue after trying to access recovery using yours. :/
If the SGS3 for Verizon is any indication, it may very well be that the Verizon GTab2 has a locked bootloader, which doesnt allow unsigned recovery images. You were doing the right steps to test though.
Here is my suggestion (I don't own this tablet, but im trying to see if I can help you out)
First, Use the image you built using recovery builder
open odin
uncheck "Auto Reboot"
Flash your Recovery Image
Make sure it didnt say "Failed" under Message, if it did, its probably locked. If not, read on
At this point, close Odin, but leave your tab attached to the PC
Hold down the power button until you get the "battery charging" image
Unplug from the PC
Hold Volume Up + Power until the first Samsung Splash appears then let go
See if CWM loads
Once you exit, CWM SHOULD tell you that ROM will overwrite it, if you want to fix that, pick Yes
You now have CWM (crossing fingers)
report back and let me know
It failed.. so I'm assuming it is locked then..
MrHyde03 said:
ODIN MODE
PRODUCT NAME: SCH-I705
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: Enabled
Click to expand...
Click to collapse
I haven't used a Qualcomm chipped device, but I'm going to guess that the above highlighted part is your issue. Until that says "Disabled" you get to have fun with whatever VZW gives you and nothing more.
Well my gs3 says that also and i have the bootloader unlocked. Both devices show it greyed out.
Being that its Verizon I will go ahead and say its locked. That means unless someone finds an exploit you won't get a custom.recovery to work.
Sent from my DROID X2 using xda premium
Yeah... that's what I was afraid of.. had high hopes though! I may never be able to crack it myself... but I'm not gonna give up. Besides, gotta learn somewhere so what better place to start. I'll probably start off by studying the gs3 unlock... seems sensible. Anyone have some tips for a noob 'developer'?
MrHyde03 said:
Yeah... that's what I was afraid of.. had high hopes though! I may never be able to crack it myself... but I'm not gonna give up. Besides, gotta learn somewhere so what better place to start. I'll probably start off by studying the gs3 unlock... seems sensible. Anyone have some tips for a noob 'developer'?
Click to expand...
Click to collapse
If you don't know where to start, I wouldn't start with the bootloader. Also, the best person to talk to would probably be Adam Outler. As far as I know, the unlocked VZW SGS3 is because they got lucky and someone sent them, or someone found, an unlocked bootloader that could be flashed to the device.
I was reading through the original s3 bootloader thread and they were saying that even with the bootloader locked, you would still be able to load a recovery and flash TW roms etc. /boot is encrypted and /recovery is not. That still prevents ODIN flashes, but not using dd from ADB. If this device is anything like the s3 (which so far as I, it is) than the same *should* apply here.
Most of the attempts I've had were from ADB using dd. Any truth to this? I don't care to have custom kernels or even CM10. Just would like to make backups and I'd like to get started with ROM development.
I kinda believe my recovery is NOT encrypted/locked because if it was I'd assume I'd get that nasty VZW Warning screen which I don't.. thus I should be able to load custom recoveries.
You still would need an exploit in order to even attempt a custom recovery. Pretty much anything out of Verizon will be locked even the sgs3 needed an exploit in order to load recovery I be leave. Your best bet as mentioned before would be to contact one of the experienced devs to see if they can help.
Sent from my GT-P3113 using xda premium
I don't think there needs to be an exploit for recovery. I've been reading up on all the original dev on that device and there were recoveries before it was unlocked.
I tryed these steps. Now I have a brink device that won't even turn on at all.. I have tryed everything I can.. Does anyone have any clues how to get this thing back up and running..
What steps? This isnt a tutorial and there currently isnt a working recovery for this tab.
Im currently compiling another one with some modifications. We'll see..
Sent from my SCH-i705 using xda app-developers app
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...
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
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