Hi everyone.
I accidently replaced a wrong lib file for my camera and now I'm unable to use the camera as well as apps like YouTube.
But anyone of you cost easily help me, if someone just would pull that file and send it to me. I already asked in the LOS thread for several days, but had no luck so far.
I assure you it is a common driver for the camera functions, and nothing else. You can easily verify that and it's the same file on anyone's S9 Vendor partition (also with LOS. since it's using the stock vendor, I guess).
I'm not sure which one is the correct vendor image and also cannot reset my phone at this time. So the best way would be to get the file from someone of you, preferably someome with LOS (but I think that doesn't really matter).
It seems that it only works with the lib from someone who is using LOS 17.1 (official)!
The file is called "libexynoscamera3.so" and located at: /vendor/lib64 (it's important tu pull the file from /lib64 and NOT from /lib.)
Please could someone do this for me? It will take only a minute. Many thanks in advance.
Or if someone knows where I can find correct vendor image for Android 10 starlte, I'd probably be able to flash it and fix my problem.
Gesendet von meinem unknown mit Tapatalk
Mega Cloud Link :
MEGA
D_Vovan_238 said:
Mega Cloud Link :
MEGA
Click to expand...
Click to collapse
Many thanks! Unfortunately it doesn't work. Did you pull it from the lib64 folder (not lib)?
And do you use the latest Lineage OS?
Maybe it has to be from that build... I'm not sure. But it still doesn't work.
Alternately I could reflash the vendor, but I'm not sure where to get it. I'm using official LOS 17.1.
Gesendet von meinem unknown mit Tapatalk
Hi ?
dtrail1 said:
Many thanks! Unfortunately it doesn't work. Did you pull it from the lib64 folder (not lib)?
And do you use the latest Lineage OS?
Maybe it has to be from that build... I'm not sure. But it still doesn't work.
Alternately I could reflash the vendor, but I'm not sure where to get it. I'm using official LOS 17.1.
Gesendet von meinem unknown mit Tapatalk
Click to expand...
Click to collapse
Yes I taked that file from lib64 folder.
You can try to download Alexis Rom, I'm using it, so it has the same file, or any other stock based rom because it has vendor image…
Then extract it to sd card and flash it in recovery by
Code:
dd if=/sdcard/vendor.img of=/dev/block/by-name/vendor
command, or if it failed then try
Code:
dd if=/sdcard/vendor.img of=/dev/block/sda19
command.
D_Vovan_238 said:
Yes I taked that file from lib64 folder.
You can try to download Alexis Rom, I'm using it, so it has the same file, or any other stock based rom because it has vendor image…
Then extract it to sd card and flash it in recovery by
Code:
dd if=/sdcard/vendor.img of=/dev/block/by-name/vendor
command, or if it failed then try
Code:
dd if=/sdcard/vendor.img of=/dev/block/sda19
command.
Click to expand...
Click to collapse
Thx. I'll try that.
It's odd though, because the only thing I did was to replace that file in /lib64 with a modified one for ZGCam, which always worked fine - until suddenly, after an LOS update, that lib wasn't existing anymore in /lib, but only in /lib64.
If you say the vendor image is included in any stock based rom, then I actually could also flash the vendor.img that's included in LOS zip? But I wasn't sure about it, because it's only 1 kb in size and I wasn't able to unpack it (while I could extract all other files in that package). But somehow LOS must have changed the vendor when it switched to lib64 driver. I supposed that your lib file doesn't work for me, because it's not from LOS.
EDIT: Flashing the vendor image didn't even change the related file! It was still the one you've sent me. Odd. I think LOS does changes to it and therefore I need that file from someone who is using LOS 17.1.
Vendor image
dtrail1 said:
Thx. I'll try that.
It's odd though, because the only thing I did was to replace that file in /lib64 with a modified one for ZGCam, which always worked fine - until suddenly, after an LOS update, that lib wasn't existing anymore in /lib, but only in /lib64.
If you say the vendor image is included in any stock based rom, then I actually could also flash the vendor.img that's included in LOS zip? But I wasn't sure about it, because it's only 1 kb in size and I wasn't able to unpack it (while I could extract all other files in that package). But somehow LOS must have changed the vendor when it switched to lib64 driver. I supposed that your lib file doesn't work for me, because it's not from LOS. So is that vendor.img (1 kb) in the LOS zip the proper one?
Click to expand...
Click to collapse
Extract it, if extracted image is less than 500 MB then it's the blank image and it is useless.
Theoretically in LOS Based rom installer vendor image not included, from what I read, it using last flashed vendor from last flashed stock rom.
I personally don't use LOS Based rom's because of not working iris scanner and other things that will not work so good like with stock rom.
D_Vovan_238 said:
Extract it, if extracted image is less than 500 MB then it's the blank image and it is useless.
Theoretically in LOS Based rom installer vendor image not included, from what I read, it using last flashed vendor from last flashed stock rom.
I personally don't use LOS Based rom's because of not working iris scanner and other things that will not work so good like with stock rom.
Click to expand...
Click to collapse
I tested everything now with the stock vendor. It doesn't even replace the lib nor does it install a new one - although the flashing process was successful. It seems that LOS somehow makes changes to it, because before the first build from october it was using libexynoscamera3.so in /lib. Then after the first october update that file suddenly was gone and now sit in /lib64. So this MUST have been changed somehow while the installation of that update. But reflashing it didn't work too.
I'm now pretty sure that it will only work with that file from another LOS user. But so far nobody provided it :/
The very last option would be to completely reset and flash everything from scratch. But I really don't want to do this now, because I've spent so much time to set it up.
Ok, you can close this thread!
I have downloaded the latest stock firmware, unpacked vendor.img.lz4, extraced the vendor.img and flashed it in TWRP. Works now!
dtrail1 said:
Ok, you can close this thread!
I have downloaded the latest stock firmware, unpacked vendor.img.lz4, extraced the vendor.img and flashed it in TWRP. Works now!
Click to expand...
Click to collapse
Thread closed per OP request.
Related
First things first, the ROM is NOT booting
This is a very early build of MIUI for the Xperia Z. It is based off the latest Cyanogenmod 10.1 RC5 release and the latest MIUI release for the Nexus 4.
All credits go to the FreeXperia team as well as the Cyanogenmod Team, whom without these forums would be very empty. Also credits to the MIUI team on this wonderful ROM
As mentioned, the ROM is not yet booting but hopefully together we can get it to work.
Progress:
I've currently managed to get it booting up to the boot animation but it freezes from there
Download - Here is my current progress so far if anyone wants to build upon it.
Download - DevHost mirror
Issues :
I need to add the lines
Code:
service shelld /system/xbin/shelld
class main
to init.rc within the ramdisk. However, the recompiled boot.img with the applied changes does not boot.
If anyone can apply these changes and get the kernel to boot it would be greatly appreciated!
Resolved, thanks to DooMLoRD
Logcat doesn't seem to work
Other issues are unknown at this moment in time.
To Do List:
[*]Compile a kernel with the ramdisk changes that actually boots
Fixed by DooMLoRD
Fix logcat on boot
Get ROM to actually boot!
Installation Instructions:
NOTE: ROM will not boot, these instructions are just for users who want to help out or debug. Thank you
Place ROM on SD card
Boot into recovery
Flash zip
Wipe data / factory reset
Reboot
Porting Steps:
These steps have mainly been taken from this thread, with the necessary changes needed.
Full credits go to the OP as well as many thanks to those who posted helpful suggestions and hints.
Step 1. Choose which ROM to use as base. I've decided to go with Cyanogenmod. I'm using the latest RC5 release, which I believe to be very
stable. However, you're welcome to use any other ROM as base but I'm unsure as to what the results may be.
Step 2. Choose ROM to port from. I originally used the MIUI ROM for the Nexus 4 but in future other devices, i.e. the Oppo Find 5, may prove to be a more viable option.
Step 3. Extract the contents of your base ROM to a folder. For example, C:\MIUI\CyanogenmodBASE\
You will have the following folders:
system
META-INF
You will also have the file boot.img
Open the folder named system. Now you will see the following folders:
addon.d
app
bin
etc
extras
fonts
framework
lib
media
semc
tts
usr
vendor
xbin
You will also have the file build.prop
Delete the following folders:
app
framework
media
fonts
Step 4.
Extract the contents of the ROM you're porting from to a folder. i.e. C:\MIUI\PortROM\
Copy the folders that you deleted from the previous step to the CyanogenmodBASE folder
Navigate to the lib folder, (located within the system folder of PortROM)
C:\MIUI\PortROM\system\lib
Copy the following files to the lib folder found in the system folder of CyanogenmodBASE
content-type.properties (used for themes)
liblbesec.so (Used for LBA guard, MIUI equivalent of SuperUser)
liblocSDK_2_5OEM.so (Used in location access)
libjni_resource_drm.so (Used for themes and DRM)
libshell.so (Shell service)
libshell_jni.so
libshellservice.so
Now, from the etc folder, (located within system folder)
Copy the file named telocation.idf , to the etc folder inside system in the CyanogenmodBASE folder.
Then, within the etc folder, navigate to the folder named permissions. Copy the following permission over to the etc folder inside the CyanogenmodBASE folder.
com.google.android.media.effects.xml
com.google.widevine.software.drm.xml
com.google.android.maps.xml
In the system folder of PortROM, navigate to xbin and copy and paste the following files to the xbin folder in CyanogenmodBASE.
su
shelld
That's all the folders and files that need to be copied over. You also need to unpack the kernel and apply the ramdisk changes that DoomLoRD did. Then you need to repack the kernel.
Finally add the system and META-INF folders as well as the repacked kernel to a zip file and you have your flashable ROM :good:
This guide is very messy and is quite rushed. I'll clean it up when I get time but I do apologise in advance. If there's anything you're unsure of about these steps just post a reply and I'll try to help out as soon as I can
I cross my fingers and hope that you can solve the problems. Bit great done this far, looking towards MIUI V5!
Sent from my C6603 using Tapatalk 4 Beta
fareeed said:
Issues :
I need to add the lines
Code:
service shelld /system/xbin/shelld
class main
to init.rc within the ramdisk. However, the recompiled boot.img with the applied changes does not boot.
If anyone can apply these changes and get the kernel to boot it would be greatly appreciated!
Logcat doesn't seem to work
Other issues are unknown at this moment in time.
Click to expand...
Click to collapse
post just the kernel.. i will add the changes u need...
also at which stage is the kernel u used getting stuck up?
PS: i tried downloading the ROM from the link you posted but the download never begins... may be u can provide alternate download link?
DooMLoRD said:
post just the kernel.. i will add the changes u need...
also at which stage is the kernel u used getting stuck up?
PS: i tried downloading the ROM from the link you posted but the download never begins... may be u can provide alternate download link?
Click to expand...
Click to collapse
Thanks Doom, adding DevHost Mirror now.
As for the kernel, I unpacked and repacked using championswimmers kernel kitchen. Editing and repacking is fine but when I flash the repacked kernel, I just get a single vibration but nothing on the screen. Have to hard reset and flash previous kernel to get it to boot again.
p.s. The guide I'm following said to leave a blank line at the end init.rc, could this have had any effect?
Here's the boot.img that I'm trying to edit
Update: Roughly 20 mins left for DevHost mirrorr :good:
Ahw, i love MIUI interface, with FullHD of Xperia Z and that colors will be wonderful!!
fareeed said:
Thanks Doom, adding DevHost Mirror now.
As for the kernel, I unpacked and repacked using championswimmers kernel kitchen. Editing and repacking is fine but when I flash the repacked kernel, I just get a single vibration but nothing on the screen. Have to hard reset and flash previous kernel to get it to boot again.
p.s. The guide I'm following said to leave a blank line at the end init.rc, could this have had any effect?
Here's the boot.img that I'm trying to edit
Update: Roughly 20 mins left for DevHost mirrorr :good:
Click to expand...
Click to collapse
here u go:
http://d-h.st/GsY
i have added the info u requested in the end of the init.rc file...
i have checked and the kernel booted on my Xperia Z...
i dont have the ROM so i cant test...
DooMLoRD said:
here u go:
http://d-h.st/GsY
i have added the info u requested in the end of the init.rc file...
i have checked and the kernel booted on my Xperia Z...
i dont have the ROM so i cant test...
Click to expand...
Click to collapse
Thanks Doom, much appreciated , 6 minutes left on the DevHost mirror guys
UPDATE: Here is the devhost mirror
Important
Instructions:
After download, replace boot.img in zip with newer boot.img that DooMLoRD has very kindly provided.
Place zip on SD card
Reboot into recovery
Backup (ROM isn't guaranteed to boot)
Flash zip
Wipe data / factory reset
Reboot
Then report here and see what happens. I'll test ASAP as well. Also if possible, please try and provide a logcat. It should be said that I was unable to get one the first time but hopefully someone can
Update 2: Just realised I was editing init.sh instead of init.rc whoops, well all in the name of learning I suppose. At least I know for next time haha
Is the kernel based on the Cyanogenmod kernel? Which recovery is included?
Michealtbh said:
Is the kernel based on the Cyanogenmod kernel? Which recovery is included?
Click to expand...
Click to collapse
Yep based on latest Cyanogenmod RC 5, I think the recovery is CWM 6.0.32
fareeed said:
Yep based on latest Cyanogenmod RC 5, I think the recovery is CWM 6.0.32
Click to expand...
Click to collapse
Thanks, should use recovery from the FOTAkernel partition then.
I'll test tomorrow if I get time
Tried using the newer kernel from DooMLoRD but still hangs at boot animation.
@DooMLoRD Do you know how I can get a log cat during the boot process so I can find out what's giving me errors? I tried the normal adb command but I'm guessing USB debugging needs to be on for that. I think there's something I need to edit in the build prop to force enable USB debugging on boot? Thanks for your help
I already tried to port miui with cm kernel and also it freeze on boot logo.
Will try to help you as much as i know starting from Monday.
Sent from my C6603 using xda premium
gm007 said:
I already tried to port miui with cm kernel and also it freeze on boot logo.
Will try to help you as much as i know starting from Monday.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Thanks, I appreciate any help I can get.
Main obstacle in my way is getting logcat to work on boot. If I can get that working, then I can get a better idea of what the errors are. I found some build prop stuff which might be worth a try
fareeed said:
Thanks, I appreciate any help I can get.
Main obstacle in my way is getting logcat to work on boot. If I can get that working, then I can get a better idea of what the errors are. I found some build prop stuff which might be worth a try
Click to expand...
Click to collapse
From which device are you porting?
I tried nexus4,but the problem is the full hd.
Sent from my C6603 using xda premium
1080P devices?
gm007 said:
From which device are you porting?
I tried nexus4,but the problem is the full hd.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
I'm not interested in MIUI but you might find this interesting.
http://bbs.gfan.com/forum.php?mod=viewthread&tid=5906702
Just put it in Google translate
I just googled 1080P MIUI or something.
The Oppo Find 5 is a very similar device to the XperiaZ.
snowman77 said:
I'm not interested in MIUI but you might find this interesting.
http://bbs.gfan.com/forum.php?mod=viewthread&tid=5906702
Just put it in Google translate
I just googled 1080P MIUI or something.
The Oppo Find 5 is a very similar device to the XperiaZ.
Click to expand...
Click to collapse
Personally I think you can ask MIUI forum for help
it seems that miui team has devoted all time toward Xiaomi Phone and ignored the existence of Xperia Z
Type this command: adb -d logcat
On your pc Before booting the phone to get logcat.
Sent from my C6603 using xda premium
WOOWWWW!!!!
REally Really great news!! miui interface are wonderful and in full HD OOOOOoooOOO, no words!! i'm waiting for news about boot!!!
Can't wait
Sent from my Kindle Fire HD 7 using xda app-developers app
Yeah Finally a MIUI rom thank you very much for trying to develop it i can't use my smartphones without MIUI, thanx DoomLord too I've always loved your work since the xperia x10, Sorry for spamming..
Hello,,,
anybody knows how to fully root emui 3.0. i've been trying to use 3.0 since it was released by Oxalis for L10 but i have a problem in rooting. I did root the phone, but i can say it is only 99% rooted, bcoz everytime i tried to delete file or app under /system/app directory files will be reverted after rebooting. i've deleted the files or app under the mentioned directory and i successfully deleted, but again, if i will reboot the phone, the apps deleted will be installed again.
Use custom E3.0 rom,unpack zip on pc,delete unwanted apps and everything you want,pack in zip again and than flash rom.This is only way (in my case) to delete unwanted apps.In any other way deleted apps return back after reboot.
Sent from my HUAWEI P7-L10 using Tapatalk
gregysk said:
Use custom E3.0 rom,unpack zip on pc,delete unwanted apps and everything you want,pack in zip again and than flash rom.This is only way (in my case) to delete unwanted apps.In any other way deleted apps return back after reboot.
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
i'll better make updater.zip than unpacking system...
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
witteswa said:
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
Click to expand...
Click to collapse
Thanks a lot... I hope this will work. coz i tried everything except this. I will install 3.0 again later. Thank you so much.
witteswa said:
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
Click to expand...
Click to collapse
thanks for this idea. i am 100% rooted now. thanks a lot.
Did you delete file set_immutable.list ?
majcomtech said:
thanks for this idea. i am 100% rooted now. thanks a lot.
Click to expand...
Click to collapse
hi, i am also trying to fully root Emui 3.0. i am currently running Emui 3.0 b602 on L10 and after rooting (CWM+Update SuperSU) same issue (with files being reverted)
now I am relying on updates.zip through CWM for downgrades,etc using sideload update through usb and sometimes feels awkward
I followed the link mentioned above and found a custom E3.0 rom named boot_HRT_emui3.0.img.
@majcomtech, is this the one file that made you 100% root? I did not see references to L05, L07 or L10 nor B602, B604 or B609. Does it mean that this HRT boot.img is valid for all P7 models, say for the whole family of p7s?
will it fully root my 99% P7 L10 B620 EMUI3.0 BETA to 100% P7 L10 B620 EMUI3.0 BETA even though is not specific to a L10 nor b602?
@Kostyan_nsk, can not find set_immutable.list file inside /system folder as I used to have, a config text file with a list of immutable folders and files.
If I flash that hrt boot image I would not need to delete that file? is that the following step, flash new boot.img then delete set_immutable.list?
thanks in advance for your advice, those seam like a lot of questions :silly:
p.d: sorry english not my native language
Printusrzero said:
@Kostyan_nsk, can not find set_immutable.list file inside /system folder as I used to have, a config text file with a list of immutable folders and files.
If I flash that hrt boot image I would not need to delete that file? is that the following step, flash new boot.img then delete set_immutable.list?
Click to expand...
Click to collapse
The principle of locking system files and folders is next: there is set_immutable binary in ramdisk of boot image that executes in boot up. This binary reads list of files and folders in /system/set_immutable.list and locks them.
So there's several ways to avoid it: delete or comment line in init.rc file in ramdisk that executes set_immutable. As I remember, it looks like "exec set_immutable 1". Or change parameter from "1" to "0". Or completely delete set_immutable binary from ramdisk. So if set_immutable won't execute, existense of /system/set_immutable.list won't affect at anything.
Or you can just delete set_immutable.list and set_immutable binary will not lock anything because it will not be able to get list of files and folders to lock.
If you don't have set_immutable.list file already, I think custom boot image with disabled set_immutable binary will not solve your issue. But you have to try anyway. If system won't boot, just revert back your boot.img via fastboot or TWRP and you won't loose anything.
I think problem is in su binary. Something with security context or permissions or something else. But it's just my humble opinion, probably I'm wrong.
Thanks Kostyan_nsk for your last post!
I unpacked ramdisk and set 'exec set_immutable 1' to 0. flashed and recovery still active.
then unpacked again and renamed immutable binary inside initrc/sbin, flashed and recovery still on
I also checked supersu binaries and updated supersu both through CWM and Google... so far all my efforts were to not avail
solved! flashing custom 3.0 kernel fixed it. Kostyan_nsk you directed me to the right direction init.rc, thanks a lot .
Hello community,
I'm currently trying to modify the stock rom for my GT-I8200n. I didn't find cwm for the S III mini VE, and the version of twrp I found was very buggy. So I need an odin-compatible flash file for my rom. I tried to modify the stock rom by downloading the .tar.md5 from sammobile, unpacked it with winrar and copied the system.img into an ubuntu-VM. After that I created a sys.img (or sys.raw, same problem) out of system.img using the simg2img-file I found somewhere here on xda, mounted sys.img (or sys.raw) and modified it. Then I unmounted it and used img2simg to create my system_new.img. Copied it to my windows system, into the unpacked stock rom folder, renamed it to system.img, overwriting the old system.img and packed everything into a .tar file using ZArc. Now while flashing my ROM, odin works on the system.img for some minutes and then shows a fail.
Does anyone know what I'm doing wrong?
P.S.: I tried simply using simg2img on my stock system.img and then - without mounting and modifying - used img2simg kn the sys.img file. Same problem with odin and I noticed that my new system.img is approximately 50 mb smaller than the stock img, although I didn't modify it.
I hope I described my problem well (I'm not an english native speaker, but did my best to make this text understandable )
Any ideas or hints that could maybe solve this problem are welcome.
Thank you,
Chris
I have the same problem
any solution ?
Hi there, I am trying to create a flashable zip of stock rom, the newest UBPLP firmware, I extracted everything from original md5 packace, converted to ext and mounted as virtual image and so on, took system and preload things, then csc stuff from cache.img, created a zip, all permissions etc etc, I have some experience.
Everything works except the fact there is no signal and wifi can't connect, can't really understand what's wrong, I know I am missing something, already tryed also flashing modem, kernel and so on, but nothing, baseband is unknown, but everything is fine with efs and imei, flashing another rom solves everything.
I really would be grateful if someone can explain me how to do this or can supply with a flashable zip of that firmware, odexed or deodexed, doesn't matter, I would like to learn how to correctly make stock rom flashable from zip package
Pdevo said:
Hi there, I am trying to create a flashable zip of stock rom, the newest UBPLP firmware, I extracted everything from original md5 packace, converted to ext and mounted as virtual image and so on, took system and preload things, then csc stuff from cache.img, created a zip, all permissions etc etc, I have some experience.
Everything works except the fact there is no signal and wifi can't connect, can't really understand what's wrong, I know I am missing something, already tryed also flashing modem, kernel and so on, but nothing, baseband is unknown, but everything is fine with efs and imei, flashing another rom solves everything.
I really would be grateful if someone can explain me how to do this or can supply with a flashable zip of that firmware, odexed or deodexed, doesn't matter, I would like to learn how to correctly make stock rom flashable from zip package
Click to expand...
Click to collapse
Try SuperR kitchen: http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296 .
Thank you @#Henkate, after lots of testing I found out the problem was in some symlinks in /system/bin folder corrupted, so the only way was to use nandroid backup and take everything from there
Have u created the flashable zip[email protected]
sm_adil said:
Have u created the flashable zip[email protected]
Click to expand...
Click to collapse
Sorry for huge delay!
Yes, I did
Hello guys,
As you know Xiaomi released a few weeks ago the kernel source for mi 8. I decided to learn something new and came until the point where I got the Image, Image.gz-dtb, and Image.gz and a dts folder.
I really tried like Anykernel, Lazyflasher EVERYTHING but it just goes into fastboot after I start. I would really appreciate your help if someone could explain me how to flash and a little tutorial.
Thank you
I am on xiaomi.eu stable MIUI 10
NightScap3 said:
Hello guys,
As you know Xiaomi released a few weeks ago the kernel source for mi 8. I decided to learn something new and came until the point where I got the Image, Image.gz-dtb, and Image.gz and a dts folder.
I really tried like Anykernel, Lazyflasher EVERYTHING but it just goes into fastboot after I start. I would really appreciate your help if someone could explain me how to flash and a little tutorial.
Thank you
I am on xiaomi.eu stable MIUI 10
Click to expand...
Click to collapse
What exactly are your step with anykernel?
Haven't you a "zimage" File?
I haven't compiled 64bit or Xiaomi kernel yet so I'm not sure what the step are: /
3lambda said:
What exactly are your step with anykernel?
Haven't you a "zimage" File?
I haven't compiled 64bit or Xiaomi kernel yet so I'm not sure what the step are: /
Click to expand...
Click to collapse
No I don't have a zImage file. I attach an picture of my structure. (https://imgur.com/a/3QOaUa2)
I really dont know whats wrong, the only thing I edited is the kernel name in the Makefile...
My steps are basically just to copy the Image.gz-dtb and rename it to zImage, but this doesn't work and also ends in a bootloop. I dont think it's the problem with AnyKernel I think with the Kernel Source, because my stock kernel is like 44 mb and mine 34 mb (compressed)... Maybe it's with the dts folder??? I dont know
I attached also an log which was recorded during bootloop.
Thanks
NightScap3 said:
No I don't have a zImage file. I attach an picture of my structure. (https://imgur.com/a/3QOaUa2)
I really dont know whats wrong, the only thing I edited is the kernel name in the Makefile...
My steps are basically just to copy the Image.gz-dtb and rename it to zImage, but this doesn't work and also ends in a bootloop. I dont think it's the problem with AnyKernel I think with the Kernel Source, because my stock kernel is like 44 mb and mine 34 mb (compressed)... Maybe it's with the dts folder??? I dont know
I attached also an log which was recorded during bootloop.
Thanks
Click to expand...
Click to collapse
Okay your boot image is "image" for sure
Can you send me your anykernel zip ?
Also never rename file in boot folder [emoji4]
And about different size it depends on toolchain used so it's normal
Envoyé de mon MI 8 en utilisant Tapatalk
3lambda said:
Okay your boot image is "image" for sure
Can you send me your anykernel zip ?
Also never rename file in boot folder [emoji4]
And about different size it depends on toolchain used so it's normal
Envoyé de mon MI 8 en utilisant Tapatalk
Click to expand...
Click to collapse
I have named it in zImage because it wouldn't work. The Path in the config is wrong, because i didn't use it anymore, I used Android Image Kitchen and flashes over TWRP
NightScap3 said:
I have named it in zImage because it wouldn't work. The Path in the config is wrong, because i didn't use it anymore, I used Android Image Kitchen and flashes over TWRP
Click to expand...
Click to collapse
Hmm I can't test now (locked bootloader :/ and need to wait 500 hour still)
But when I'll be unlocked I'll try and test and report to you
Thank you man Hope to get my first kernel booted up then haha