Database Users

[Q] Issues after installing Custom boot.img

Hi,
I have downloaded kernel sources from HTC for wildfire and compiled zImage. using unpack and repack scripts I successfully installed the boot.img via update.zip. Now I see the device reboots fine, but I cannot unlock the screen, and none of the keys are functional.
I have no Idea what is still missing or have I done something wrong?? your help is need here.
Indeed I tried to compile jacobs kernel image from github but no luck.
Regards
bram

[Q] CWM and some boot questions

Hi guys, i just want to learn something here that i dont quite understund
A) We normally for all roms intall D2Bootsrapper, then boot reboot into recovery
Once in we flash bootmenuv2.zip
and then we start flashing custom roms...
Whats the difference in D2bootstrapper and bootmenuv2? is there a newever version of this files?
B) Some roms used to recomend applying a sbf fix, a small sbf, is that still needed?
cuz i never applied it... lol
C) What kind of boot hackery are we currently using? 2ndinit 2ndboot?
Thanks!

A)
D2Bootstrapper is a hack originally created for DroidX/Droid2. It mimics the /system/bin/logwrapper binary that is normally executed by android initialization scripts on the early stages of system boot. More info here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Bootmenu is hack developed for Defy based on the same concepts of Droid2bootstrapper (actually it hijacks the same binary) but also included the features of 2nd-init which were ported by me from Milestone1 to Milestone2. Details here:
Bootmenu - http://forum.xda-developers.com/showthread.php?t=1026853
2nd-init - http://forum.xda-developers.com/showthread.php?t=998425
B)
You will need to flash SBF if:
- The ROM you're trying to flash requires kernel and devtree from other version than the one currently on your phone; and
- The update.zip doesn't include the images and commands to flash new kernel and devtree (my MIUI ROM includes everything, thats why I call it all-in-one).
C)
2nd-init.

r2beta0 said:
A)
D2Bootstrapper is a hack originally created for DroidX/Droid2. It mimics the /system/bin/logwrapper binary that is normally executed by android initialization scripts on the early stages of system boot. More info here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Bootmenu is hack developed for Defy based on the same concepts of Droid2bootstrapper (actually it hijacks the same binary) but also included the features of 2nd-init which were ported by me from Milestone1 to Milestone2. Details here:
Bootmenu - http://forum.xda-developers.com/showthread.php?t=1026853
2nd-init - http://forum.xda-developers.com/showthread.php?t=998425
B)
You will need to flash SBF if:
- The ROM you're trying to flash requires kernel and devtree from other version than the one currently on your phone; and
- The update.zip doesn't include the images and commands to flash new kernel and devtree (my MIUI ROM includes everything, thats why I call it all-in-one).
C)
2nd-init.
Click to expand...
Click to collapse
Thanks man!

that's very helpful, thanks!
Sent from my ME722 using XDA App

thanks it helped a lot!

[GT-I9070][Kernel][GINGERBREAD] Stock Kernel + TWRP Recovery for Galaxy S Advance

This kernel will provide you the standard stock kernel and also includes TWRP recovery.​
( disclaimer )
I AM NOT TO BE HELD RESPONSIBLE IF YOU DAMAGE YOUR PHONE
Using Odin to flash this kernel WILL increase your binary counter.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( features )
- Team Win Recovery Project 2.2.1
- CIFS Support
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( how to install using Odin )
1. Restart into download mode by pressing Power + Home + Vol Down
2. Start Odin, and flash the attached kernel as PDA.
Remember to extract the attached file only once. if you end up with a kernel.bin.md5 you extracted twice!
Do not use the PIT, do not have any options checked except for "Auto reboot" and "F. Reset Time"
3. Wait for the device to reboot
( how to install using DD )
This method does not increase your binary counter, but your phone needs to be rooted so you can perform this!
IF YOU'RE NOT FAMILIAR WITH DD I RECOMMEND YOU TO AVOID THIS METHOD
1. Extract the attached file twice. You will end up with a kernel.bin.md5 file
2. Put the kernel.bin.md5 file to /sdcard
3. Start adb shell
4. Do the following commands:
Code:
$ su
# dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15
# reboot
5. Wait for the device to reboot.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( special thanks )
- Team Win for creating this awesome custom recovery.
- @Chris41g for starting the TWRP port.
- @hackbob for helping with the kernel issues.
( donations )
if you think that think that the work I put in this kernel is donation worthy,
then click the following link and buy me a beer/coffee/etc...
Donate via Paypal :good:
Enjoy! and don't forget to hit the thanks button
if you find any issues with this kernel, please report!

reserved.

Can you give me just compiled zImage i.e kernel image ASAP?

varun.chitre15 said:
Can you give me just compiled zImage i.e kernel image ASAP?
Click to expand...
Click to collapse
You can download the package and extract the kernel.bin.md5.
While building it's generated as zImage and after renamed to kernel.bin and md5ed for Odin

Well actually, that is not what I need because kernel.bin.md5 contains initramfs which is known as ramdisk usually. But I only need kernel i.e zImage which I am planning to repack to boot.img
Correct me if I am wrong

varun.chitre15 said:
Well actually, that is not what I need because kernel.bin.md5 contains initramfs which is known as ramdisk usually. But I only need kernel i.e zImage which I am planning to repack to boot.img
Correct me if I am wrong
Click to expand...
Click to collapse
Yep you are right, sorry for the misunderstanding.
I can build it (from Github) for you without the ramdisk but I'm not sure it will work correctly without the driver added from the ramdisk to the kernel image during the build.
---------- Post added at 05:27 PM ---------- Previous post was at 05:22 PM ----------
Just to be sure...
I'm trying to compile cm7 and the intrafms are added with the kernel while building the boot.img, because in the intrafms that we are adding to kernel image we are basically adding the modules for wifi,bt, etc...
You sure you don't need them?

hackbob said:
Yep you are right, sorry for the misunderstanding.
I can build it (from Github) for you without the ramdisk but I'm not sure it will work correctly without the driver added from the ramdisk to the kernel image during the build.
Click to expand...
Click to collapse
Ok can you do that, test it and report back ASAP?
This is needed before I release my ROM
btw I think we should move on to main DEV thread
Post your next reply over there

@varun.chitre15
you can try to build it from source...
the source code is available on github: https://github.com/diego-ch/android_kernel_samsung_janice

hackbob said:
[/COLOR]Just to be sure...
I'm trying to compile cm7 and the intrafms are added with the kernel while building the boot.img, because in the intrafms that we are adding to kernel image we are basically adding the modules for wifi,bt, etc...
You sure you don't need them?
Click to expand...
Click to collapse
Oh great!
Can you get me the boot.img compiled while building
I will take what all I need from it
---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------
diego-ch said:
@varun.chitre15
you can try to build it from source...
the source code is available on github: https://github.com/diego-ch/android_kernel_samsung_janice
Click to expand...
Click to collapse
Well actually I am trying to avoid that because I have no experience in kernel development

Can i extract it from the rom? I got boot.img and recovery.img, is that you need?
Sent from my GT-I9070 using Tapatalk 2

Exactly!
Attach the boot.img

varun.chitre15 said:
Exactly!
Attach the boot.img
Click to expand...
Click to collapse
i sent you a pm

Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...

Would it be possible to create a kernel with recovery for Advance with NFC chip?

xCode195 said:
Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...
Click to expand...
Click to collapse
Have you setup USB drivers of your phone?
Waiting for device indicates, Superone click is unable to contact your phone.

Am I the only one with TWRP restore not Working properly?
Backedup the default partition (system, data and another that I don't remember), Restored, everything seems fine (no error on twrp) but after a reboot the phone goes into bootloop.

varun.chitre15 said:
Have you setup USB drivers of your phone?
Waiting for device indicates, Superone click is unable to contact your phone.
Click to expand...
Click to collapse
Yep I tried installing them again and it got stuck on the same step but now i also get Hardware ID Failed popup when I connect the device..
Should I reflash the kernel or do something else?

Iv backuped and restored a few times and its ok
Sent from my GT-I9070 using Tapatalk 2

hackbob said:
Am I the only one with TWRP restore not Working properly?
Backedup the default partition (system, data and another that I don't remember), Restored, everything seems fine (no error on twrp) but after a reboot the phone goes into bootloop.
Click to expand...
Click to collapse
I was testing antonio's rom yesterday and before that I made a full backup.
today I restored my backup and everything was fine.
get me a logcat, a dmesg log and also a recovery.log so I can take a look on whats wrong.
xCode195 said:
Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...
Click to expand...
Click to collapse
you can also use CWM Flasheable SuperSu from Chainfire instead of supéroneclick
do you have an external sdcard? it wont work with internal memory.

diego-ch said:
you can also use CWM Flasheable SuperSu from Chainfire instead of supéroneclick
do you have an external sdcard? it wont work with internal memory.
Click to expand...
Click to collapse
I would try that if I could get TWRP to read my sdcard,it says its browsing the sdcard but none of my files or folders are there and its just empty.When i reboot into the system everything is there but not in TWRP...

[Q] Enable ADB / USB Debugging with a broken screen

Any kernel developer can help me with this?
I have broken my lcd of my s5 and no usb debugging enabled.
So i read this here
i suggest you contact a kernel developer to automatically enable it in the default.prop and sideload the kernel in recovery!
Click to expand...
Click to collapse

brunocssoares said:
Any kernel developer can help me with this?
I have broken my lcd of my s5 and no usb debugging enabled.
So i read this here
Click to expand...
Click to collapse
I'm a kernel developer but still new here on samsung so I can't compile a kernel for s5 yet but I can explain to you the process and maybe you have the knowledge I still don't have.
1. Get any custom kernel that's compatible to your s5.
2. Extract the ramdisk from the kernel.
3. Unpack the ramdisk and edit the rc file that's responsible for enabling adb(I think it's init.rc).
4. Repack the ramdisk.
5. Make a new boot image using the modified ramdisk and the zImage you got awhile ago when you extract the ramdisk.
6. Flash the resulting boot.img using fastboot by typing "fastboot boot <boot.img file>"
Please not that the fastboot command doesn't permanently flash the kernel and will revert back to the previous kernel after reboot.
On a second thought... I'm not sure but you can try flashing one of the recoveries here or a AOSP kernel. Most of them have USB Debugging enabled by default. At least that's true base on my past devices.

Thank you for the answer!
But unfortunately i don't know how to do this things. So, I will study a little about this and if I get a solution i will post here!
Try hard always!
One more thing: Can I use other cellphone's tutorial to do this? Like this : http://forum.xda-developers.com/showthread.php?t=1262656
sorry for my horrible english!

Yoga Tab 2 Kernel Compilation

Has anyone else made any serious attempts at compiling a kernel? Prompted by doctorow's thread about the wakelock issue, I got interested in compiling a kernel so it could actually be fixed. For anyone who's tried at all, there are obviously some missing files in Lenovo's release.
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
P.S.: I'm not really sure if this belongs in the dev section or not? Sorry if it's in the wrong place, but I can't start threads there anyway at my current post count.

iampanis said:
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
Click to expand...
Click to collapse
Interesting, I haven't even gotten that far when I tried to compile them. The sources are most likely not up to date or even representative of the actual firmware kernel. For example, when I looked at the battery driver, I noticed in the published sources, the polling interval was hard-coded in such a way that it would completely ignore the setting of the poll_interval kernel parameter. But we know that this is not true for the actual firmware which is in fact respecting the setting of said parameter.

@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.

Olivier said:
@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.
Click to expand...
Click to collapse
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!

raenye said:
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!
Click to expand...
Click to collapse
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.

Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
Hello, I have a 1050F too is somebody tried this kernel on 1050F? Is it possible to support wake gesture kernel extensions with this kernel?

Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....

raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....
Click to expand...
Click to collapse
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.

corasman said:
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.
Click to expand...
Click to collapse
The kernel goes to the boot partition. So 2nd option.

raenye said:
The kernel goes to the boot partition. So 2nd option.
Click to expand...
Click to collapse
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.

corasman said:
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.
Click to expand...
Click to collapse
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)

raenye said:
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)
Click to expand...
Click to collapse
Yes to all.
I wondered if the command slashes were the right way / or \ the way I used is what I used to unlock the bootloader and install TWRP.
I have tried the slashes the other way and get the same result, as in \ .

raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Click to expand...
Click to collapse
Hmm, I'm getting a high battery_wake_lock (on the April OTA firmware) -- even when running this kernel!
Any idea how can this be?

Hi,
I was trying to play a little bit with kernel provided by @Olivier and @Grarak ...
1. Binary Image kernel-yt2-20160327.img boots up fine on 1050l, but LTE is not working. Rest seems to be fine...
2. In next steps I replaced initrd.img with a little modified stock one - and LTE started to work - I removed from initrd almost all modules leaving only bcm43241.ko.
3. Battery wakelock problem seems not be resolved - brief check at bq27x00_battery.c in repository shows that wake_lock is still set under bq27x00_battery_suspend_resume()
... so I trying to fix this battery driver but I have problem with kernel - I can compile it successfully, but it doesn't boot
@Olivier:
1. Which branch was used to build kernel-yt2-20160327.img?
2. Which config did you use ?
My procedure using android-ndk-r12b toolchain:
# git clone ...github.com/lenovo-yt2-dev/android_kernel_lenovo_baytrail
# export PATH=~/android_yoga/toolchain/bin:$PATH
# export CROSS_COMPILE=x86_64-linux-android-
# export ARCH=x86
# make cyanogenmod_YT2_10_defconfig --- if this right config?
# make -j8 ----- lot's of warninigs, but kernel is compiled sucesfully.
# abootimg --create boot_test5.img -f bootimg.cfg -k bzImage -r initrd.img ---- bzImage from arch/x86/boot
> fastboot.exe flash boot boot_test5.img
... kernel stuck somewhere, it's doesn't even come to Zygote phase (lenovo animation). Is there any way to see kernel boot messages ?

Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards

airmalaga said:
Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards
Click to expand...
Click to collapse
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.

Thx :good:
jasfasola said:
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.
Click to expand...
Click to collapse

jasfasola said:
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
Click to expand...
Click to collapse
Cool, could you push your patch to GitHub?
jasfasola said:
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
Click to expand...
Click to collapse
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.

Olivier said:
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.
Click to expand...
Click to collapse
Fixed. That was quite easy. Driver al3320 was in place. The problem was permissions set by script init.byt_t_ffrd8.rc in initrd. By default it's root/root, but it should be system/system. I already corrected paths and checked it - it's working. If you could give me permission to repo I can push the patch.
BTW: I see lot's of things are being hard-coded into initrd scripts. Since we changed config kernel, all those scripts must be checked. I can try to do it in free time...but some things are platform depended so, another original initrd from lolopop on 830f would be nice to compare...

jasfasola said:
so, another original initrd from lolopop on 830f would be nice to compare...
Click to expand...
Click to collapse
What do you need exactly? @jasfasola