Search results

I think there are two different issues here. In hardboot you have to reserve a "hardboot page". This is statically allocated by the kernel as part of the board file as your quoted code shows. The hardboot page doesn't actually store the kexec kernel image, but instead contains the address of...

Hardboot is ARM-specific. If you look at the patch it uses ARM assembly and hooks into SoC specific stuff.

1. The root= option will automatically mount that given device as the root partition (aka /). If you use root= you do not need an initramfs at all, because the kernel will mount the partition and run the /init script automatically. If you don't use a root= command or wish to run more complex...

You don't need them. My sloppy work is showing lol. I took most of that from another kexecboot from the HP TouchPad. Chances are your Tab3 doesn't use LVM, though the TouchPad did so that's where that came from. You can remove it. The tssrv binary is the userspace HP TouchPad touchscreen...

Step one is to get a kexec-capable kernel working. Kexecboot is just a frontend for kexec. There are two options - normal kexec and kexec-hardboot. I managed to make hardboot work with the Note 1 using some patches but haven't been successful with either on the Note 3. I don't know about...

I'm still here. I kinda gave up temporarily after running into too many roadblocks, then I bought a fancy RGB keyboard and lost track of the project. Then the holiday season took up the rest of my year. I want to get back into this, but I think I'm going to try and get Debian running natively...

Yeah, figured that out last night. I found a guide to recalibrate the sensor that worked perfectly. I tried cleaning the outside, but it didn't work and I don't feel like tearing the whole phone apart to clean it.

Awesome, recalibrated my sensor with the efs file and it worked perfectly. I never had an issue with the sensor until now (a month past one year of owning the phone, plus Knox is long tripped so warranty isn't happening). If it gets worse I'll take it apart and clean the sensor but for now the...

I'm having an issue where the proximity sensor only triggers on entering close proximity, not when leaving close proximity. This is noticeable when I get a call, hold the phone up to my ear and the screen turns off but take it away and the screen stays off. I can verify the issue reading the...

No, I just enabled the FIQ debugger in the .config (the code is already in the kernel) but it doesn't compile, FIQ_START is undefined. ryanbg said he was working on it so I am going to wait to see if he has already solved this as to not duplicate work. Have you looked into getting a serial...

hsbadr: Still interested for sure! I don't know what all good Hangouts will be unless we're all online at the same time though. ryanbg mentioned FIQ debugger in a PM he sent me so I'm going to investigate that route on the host kernel and try to get it working. Otherwise the memory tagging...

Trying to figure out /dev/mem <--> /dev/kmem mapping. It is getting to the code that turns on the MMU and after that the memory mapping should be changed, so to tag physical address 0x50000000 I need to know what the corresponding kmem virtual address is. From what I've found, at least in...

Sounds good, I'll take a look at those patches. My kexec-tools binary is the one Tasssadar has on his github for kexec-hardboot, but I guess now that I'm trying to use non-hardboot kexec I should use a different kexec-tools. Either way, I confirmed that execution is getting to the main kernel...

I just found the -C option for hexdump which corrects the endianness issue: [email protected]:/ # /data/local/viewmem 0x2700000 0x100 | hexdump -C...

Looking at this code: mov r8, r2 @ save atags pointer ldr r9, =0x50000000 str r0, [r9, #0] str r1, [r9, #4] str r2, [r9, #8] ldr r10, =0xFFFFFFFF str r10, [r9, #12] #ifndef __ARM_ARCH_2__ produces this output: / # hexdump test.bin 0000000 0000 0000 ffff ffff 1000 0000...

If the kexec-mod changes are all in individual commits that don't change anything else I should just be able to cherry pick them into the CM11 kernel that I'm testing on so I can mess with kexec mod as well. Ultimately though, if it turns out we're all getting the guest kernel loaded, the issue...

We are researching kexec in the development forum. I've read that someone figured out how to load modules on the AT&T kernel (disabling selinux I think). I'm on the N900T unlocked variant but even normal non-module kexec is broken at the moment so once we figure out what's blocking it it...

What's the status of your kexec? Have you attempted to load a guest kernel on the N900V? If so, did you get a log of what happened up to the reboot? Making the changes I mentioned in my previous post it gets all the way through machine_kexec(), prints "Bye" and then my console stops...

Tracked it down further. It crashes after "preparing kexec_start_address" is printed in the following code: void machine_kexec(struct kimage *image) { unsigned long page_list; unsigned long reboot_code_buffer_phys; void *reboot_code_buffer; unsigned int temp; printk(KERN_EMERG...

I just loaded a new test kernel to play with. This time I used standard cm-11.0 master branch (no hardboot or other changes) with CONFIG_KEXEC and CONFIG_PROC_DEVICETREE set. This should provide enough to perform a non-hardboot kexec I think. My initramfs is very basic, just opens a busybox...

I'm going to go back and try to figure out why normal non-hardboot kexec isn't working. If the bootloader is erasing memory hardboot may not be a good option. I was having an issue rebooting before and I'm not sure why.

Ok, I got the hardware serial console hooked into my kexecboot initramfs so it opens a terminal on boot. Since my initramfs is very simple and limited there should be no other interference besides the kernel. I then used viewmem to record the first 256MB of RAM which I'm going to dig through...

Go ahead and post it.

I think this is it: http://blog.maurus.be/2011/01/23/samsung-i9000-irom-dump/ I looked around and found that and it seems to do the same thing as OP's binary, not sure if it's the same but it's functionally identical and good enough for what I need.

It appears this "secret" serial port is present on all recent Galaxy devices. I found the guide which demonstrates it on the S3, heard about the possibility of the serial port reading a kexec thread in the S4 forum, tested it on my Note 3, and now I've gone back and plugged it into my Note 1...

Do you have the source code for this? I want to build it into my boot.img for kexec but I need it to be static compiled for that to happen as it's a bare minimum rootfs.

Serial port works! I got a nice serial console that even shows bootloader messages before booting. Now we should be able to debug kernel boot-up easier.

I just got it working as well! I didn't have a 619K resistor, nor did I have even 100K so I scavenged through a box of old parts and have a string of various resistors, pots, etc. to add up to 615 or so K. Then I whacked in my PL2303 breakout board and got data spewing out. I'm not seeing any...

Just tried viewmem with the address 0x10000008 and length 0x100000 as is the sec_log= in cmdline. I got the bootloader log which contains the kernel, ramdisk, and dt addresses. No Linux kernel log though unfortunately.

Sounds good, I'll experiment with this tonight or over the weekend. I need to find my sacrificial USB cable and figure out a combination of resistors for 619K. If it's 3.3V I have some PL2303 breakout boards from eBay that do USB to 3.3V serial so that's perfect.

I'll try it. I don't have Samsung's secret menus since I run CM though, and using it as is gives no output. Are the addresses different on the Note 3? I have some lines sec_log= and sec_dbg= in kernel cmdline with addresses.

I just found this: http://www.de7ec7ed.com/2013/09/uart-dongle-samsung-galaxy-siii.html The Note 3 may have a serial port (UART) hidden in the USB connector. If true (which I've heard mention of in other threads) this could mean a console to see kernel boot messages on. I have a sacrificial...

I think I may have found info on the potential serial port. Apparently on some Galaxy devices there is a UART available on the USB connector if you use a special cable. http://www.de7ec7ed.com/2013/09/uart-dongle-samsung-galaxy-siii.html I don't know if the Note 3 has this but I want to give...

Here is my latest code. I applied the hardboot patches which should work on unlocked bootloader. I'm using the same kernel as both host and guest, though with different initramfs. https://github.com/CalcProgrammer1/android_kernel_samsung_hlte/tree/kexec_hardboot_test1

Here is my code if you want to take a look. I had to comment a few shutdown things out because they were crashing the shutdown process and preventing kexec from happening. I also added RAM console. Edit: The code...

The issue is that I have the hardboot patches applied and the kexec-tools for hardboot/devicetree as well but after it does successfully redirect execution to the new kernel it seems to lock up after this. I'm stumped at this point as it is virtually impossible to debug without some form of RAM...

So last I heard everyone was getting stuck when attempting to boot the new kernel out of kexec. Any updates on this front? That is where I got stuck with kexec-hardboot as well and I'm stumped as to where to go from here.

Does the Note 3 have a serial port? I think I'm stuck at the same spot as you on my kexec-hardboot implementation. I tried both hardbooting and normal kexec and it hangs on both. I enabled RAM console, but to no avail, nothing showed up other than the previous kexec host kernel's log. If it...

It hasn't, I'm not sure why everyone's so scared of tripping knox. I tripped it on like day one of buying the N900T (pretty much one year ago) and it's been nothing but awesome. CyanogenMod on the Note 3 is incredible.

I've been following hsbadr's thread for module-based kexec as well. Hardboot seemed the simplest route for bootloader-unlocked devices while module-based works on locked as well. I have the unlocked N900T so I went for hardboot. I managed to get RAM console/last_kmsg working on the Note 3 to...

Are you porting to the S4 or S5? If it uses device tree then it's going to be a bit more work than what I did for the Note 1. The Note 1 uses ATAGs which the stock kexec-tools handles no problem, but on the Note 3 which I'm also attempting to port kexec-hardboot/kexecboot to it uses device...

Does anyone have any information on how kexec with dt.img is supposed to work? I'm working on an alternative method using kexec-hardboot for the bootloader-unlocked variants and I can get the phone to reboot, but the kernel never runs. I've ported Tasssadar's kexec-hardboot patch as well as...

I use MEGA because Dropbox banned my sharing permission because I had too many downloads. My early CM11 builds for the Note 3 were really popular before the official nightlies started :) MEGA doesn't seem to have that limitation.

Huh? I linked to a MEGA folder. I can view it just fine...are you using a weird mobile version or something? Try opening the page in a desktop browser.

I'm calling kexec as so: # kexec --load-hardboot --mem-min=0x50000000 zImage --initrd=initrd.img so I think I'm already doing that. My test kernel is LeanKernel which I unpacked the boot.img into zImage, initrd.img, and dt.img. First thing is I most likely need to pass the correct command...

Yeah I was just joking around.

Just now root'in? You should've rooted a long time ago! :P Using Android without root is a nightmare!

The Note 3's panel is a command mode panel while the Note 1's panel is video mode. I'm not sure about the Note 2 as I don't have one but if it worked for you it was likely video mode as well. In video mode it works like you'd expect any display to work - the framebuffer memory is automatically...

N900T, so bootloader-unlocked. It will be doubly hard to do on the N900A since you'll have to compile as modules rather than just compile your own kernel, at least unless you guys get kexec (non-hardboot) working on the locked variants. You should be able to mess around with the framebuffer on...

You can also just dump your rootfs in /data. Since Note 3 is datamedia-based it has a huge ext3 data partition shared for apps and user data. You can take advantage of this by sticking your chroot there and having access to shared space. Then just write a script to chroot into /data/debian or...