Hi all,
I have been looking into compiling the kernel and TWRP for this device.
For the kernel, it compiles but does not boot (Will invvestigate later ).
The TWRP does not boot, most likely related to boardconfig.mk. I am unable to find the kernel base or offsets. Can anyone assist in discovering this information? I have tried unpacking boot.img and the current tools does not show this information.
Shaky156 said:
Hi all,
I have been looking into compiling the kernel and TWRP for this device.
For the kernel, it compiles but does not boot (Will invvestigate later ).
The TWRP does not boot, most likely related to boardconfig.mk. I am unable to find the kernel base or offsets. Can anyone assist in discovering this information? I have tried unpacking boot.img and the current tools does not show this information.
Click to expand...
Click to collapse
Hello. I manage to create TWRP for this device.
It is currently tested on a device running the laster firmware RUI 4.0_C.13 but it should work in RUI 3.0. Decryption works, MTP didn't yet.
Related
Hi dear personal XDA developer. I would like to understand the whole structure of the operation of the platform. Desdo beginning of the boot by the end of the boot. Understanding how it is assembled in the form of the System Tree. In Order crescente.Tipo when a kernel is installed is loaded before or after the CWM. The CWM backups restores a Kernel? The fastboot is loaded before the ROM? or is part of the ROM Fastboot? I need to understand how it works the Tree of the Order of the boot startup. What it is first loaded? A Kernel ROM and improperly installed, can block the installation of a new kernel, if so how to install a kernel when the kernel fastboot no longer installs. How do I copy my kernel for security backup?
Hi,
I don't try to flood, just to increase my chance to have any help
I want to build a custom module for my GTi9300. Since the module need to be compiled whith the same kernel on the phone, i tried to build and flash a kernel from source (aka zImage). Since fastboot is not available on GS3, I just want an alternative tech to boot my gs3 with my built zImage.
I build the source from stock kernel samsung opensource database (update 8) and receive the zImage file.
I made a backup with cwm and unpack the boot.img with a perl script, then repack a new boot.img with my zImage as kernel and the ramdick from unpack but cannot boot with new package.
Could someone maybe give me a kernel source and the right corresponding package to boot it. Or maybe just a good way to make the whole process.
------------------------------------------------------------------------------------------------------------------------------
Moreover if someone can help me directly about the module, he's very welcome.
Without having the same kernel on the phone, I already tried to insmod my module. I've got first some version error, with the module_layout. Even if I correct it the module still doesn't load. In the kernel source, I modify the Subversion in the kernel to match with the one on the phone. But the compilation result add a "-gc33f1bc-dirty" to the end. Maybe I miss something to do before the compilation
Please post all questions in the Q&A section.
Thread Moved and Closed as you already have a thread going for this over there.
Hello,
I try to port Cyanogenmod to my tablet (codename: hwt1a21l/chipset: MSM8916). I build a recovery image according to the CM-Wiki. Target was CM11 because the tablet is based on Android 4.4.4 and huawei have specific downloads for 4.4.4 (kernel source). If this would work, I go further with current CM releases.
After boot into fastboot/rescue and flash the CM-recovery, the tablet restarts repeatly in rescue/fastboot (every time I press the key combination for recovery). If I flash the stock recovery, the stock recovery displays (if I press the combination for recovery).
If I execute a "fastboot boot"-command with my custom image, the output says "signature checking failed". (with "fastboot boot" on an official image, there is no problem, of course)
Bootloader is unlocked. Root access is denied (su command not found and I cannot search through the bin-directories - permission denied). I tried SuperSU, Fararoot, Kingroot, Kingo-Root. If I upload a busybox executable to the device, the shell command of 'busybox su' prints out an error about 'setuid'. A 'chmod s' doesnt work (permission denied).
I have two logs. One log for a working recovery with very detailed information and one with the pre-boot process.
Which steps can be performed to go further? Any hints are welcome
I thought about a custom aboot, sbl-hacking, etc but I didnt find any useful information for this case. (ok, I can buy IDA, which is a little bit expansive )
I read documentation about boot-image signing, but it looks like, that CM do this stuff for me? (keys-file in res is updated)
EDIT: I have no attachments button below my message form?!
Hi I have tablet with similar specs (T1-821L) and also want to compile twrp for it. I haven't much time to do this but I can give you advice to search github for device tree for similar device and modify it later. It's the sources I tried to suit to my device: https://github.com/surdupetru/g620s_twrp. I read also that cyanogenmod sources are more compatibile with Huawei devices but you can encounter problems during compilation. Omni sources are easier to compile from but contains outdated repos which also can brake the compilation and you should drag and drop manually them from cyanogenmod. I suggest you to start with older sources like cm11, cm12.1 or omni 4.4, 5.1. You can also ask more experienced devs on IRC: http://webchat.freenode.net/?channels=twrp or here: http://forum.xda-developers.com/showthread.php?p=32965365 and also g620s devs. Hope this helped you a bit .
I think the problem is the signature validation. It looks like, CM, OMNI, TWRP, etc. doesnt sign the Image with an (appropriate) certificate, that the Huawei accepts.
To fully confirm this assumption, I try to debug with an UART and/or AudioJack "device".
4got said:
Hi I have tablet with similar specs (T1-821L) and also want to compile twrp for it. I haven't much time to do this but I can give you advice to search github for device tree for similar device and modify it later. It's the sources I tried to suit to my device: https://github.com/surdupetru/g620s_twrp. I read also that cyanogenmod sources are more compatibile with Huawei devices but you can encounter problems during compilation. Omni sources are easier to compile from but contains outdated repos which also can brake the compilation and you should drag and drop manually them from cyanogenmod. I suggest you to start with older sources like cm11, cm12.1 or omni 4.4, 5.1. You can also ask more experienced devs on IRC: http://webchat.freenode.net/?channels=twrp or here: http://forum.xda-developers.com/showthread.php?p=32965365 and also g620s devs. Hope this helped you a bit .
Click to expand...
Click to collapse
I have the very same device (T1-821L) did you have any success with TWRP?
Con_Sole said:
I have the very same device (T1-821L) did you have any success with TWRP?
Click to expand...
Click to collapse
Unfortunetly no. I started modifying this tablet month ago and tried many things like: replacing kinguser with supersu but without success and repacking system.img extracted from stock firmware to place su binaries inside but also without success. I thought about bringing supersu to device without twrp because there is FlashFire but if it's impossible I will try to compile twrp.
I have been trying to build a custom aosp based ROM for pixel 4a, I have made changes to few xml files that goes into vendor/etc/ folder. I built a script to extract vendor blobs from the official vendor image provided by google and also generated build instructions for corresponding files.
I'm able to build the vendor image successfully. All the vendor files are present in the custom built vendor img, when I checked.
After flashing the images, the phone gets stuck in google logo.
I have made sure that bootloader is unlocked., osp version and vendor build version match.
1. Is there a way to build vendor image? Is my approach correct?
2. How can boot loop be debugged? -- ADB is not available at this point of time in boot process.. I'm also not able to boot into recovery, I keep getting bootloader screen.
Any help, links, refs, guides would be helpful
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
toolhas4degrees said:
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
Click to expand...
Click to collapse
I'm able to flash the vendor image. I don't want to root the phone. When I use the official vendor image, the phone boots but not when I use vendor image that I built. Is there a way to build vendor image? or How can I debug boot loop?
toolhas4degrees said:
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
Click to expand...
Click to collapse
Yes, he can use magisk manager to patch the image then flash them in fastboot mode using adb like you said
poppopret_ said:
I have been trying to build a custom aosp based ROM for pixel 4a, I have made changes to few xml files that goes into vendor/etc/ folder. I built a script to extract vendor blobs from the official vendor image provided by google and also generated build instructions for corresponding files.
I'm able to build the vendor image successfully. All the vendor files are present in the custom built vendor img, when I checked.
After flashing the images, the phone gets stuck in google logo.
I have made sure that bootloader is unlocked., osp version and vendor build version match.
1. Is there a way to build vendor image? Is my approach correct?
2. How can boot loop be debugged? -- ADB is not available at this point of time in boot process.. I'm also not able to boot into recovery, I keep getting bootloader screen.
Any help, links, refs, guides would be helpful
Click to expand...
Click to collapse
Did you already check the tutorials or how-to's available on XDA e.g. the tutorials of @AlaskaLinuxUser like
[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...
forum.xda-developers.com
or
[Guide][Video Tutorial] Intermediate to Advanced Custom Rom and Kernel Building
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it is helpful to you in your Android career! Praise God...
forum.xda-developers.com
The XDA University might also be of good help:
XDA-University
Tutorials, How-To Guides and More. Learn about mobile phone development, hacking, flashing, rooting and many other topics!
forum.xda-developers.com
Just search a bit and you'll find much more.
Hi
In order to debug the boot process on my build of Ubuntu Touch for the P20 Lite, I need to get access to console-ramoops or last_kmsg from my build. Furthermore, I have to use a recovery image that I can flash over erecovery. Currently I am using TWRP-9.1.img (Gaguga), but I get the impression it does not support this. Am I right?
If so, which recovery image should I use?
I realize the kernel of my build also needs to support this. I am checking this also, but not sure which kernel configs need to be enabled, so any help here would also be welcome.
Looks like I found the solution myself. The last recovery mentioned in this guide fixed the issue.