Mate 9 bootloop after Xposed install - Huawei Mate 9 Questions & Answers

Mate 9 bootloop after Xposed install - Huawei Mate 9 Questions & Answers

Hello there.
Long story short: I have a Mate 9 MHA-L09 running on latest Oreo update which was rooted (with bootloader unlocked of course) and worked fine. I've installed Xposed (without making a backup, nice job me …) and, unfortunately, I'm now stuck in bootloop.
I've tried following methods:
starting in fastboot mode to recover using HiSuite but my Mate 9 isn't supported.
Boot on TWRP and tried to wipe data cache and dalvik but it didn't work.
Tried to install Oreo and Nougat updates from TWRP (with 3 archives on SD card: update.zip, update_data_public.zip and update_all_hw.zip) however I'm also getting and error when trying to install the first zip file (error 7 - "update_huawei_pkg_from_ota_zip: update package from zip failed")
I also tried the HWOTA method but after starting in TWRP and connecting a USB cable, the script seems frozen.
Maybe I'm using an incorrect function of TWRP? Or there is an easier method?
Any help would be greatly appreciated.
Thanks guys!

Tried to install latest MHA-L09C33 firmware and got an error 9 on TWRP.
Here is the log: https://pastebin.com/Yc0bnbfk

I'm trying to invoke @ante0 as he seems quite an expert
The current situation is the following:
Phone is bootlooping
I can start in fastboot (PHONE Unlocked, FRP Unlock)
I can start on TWRP. I did install the version @ante0 suggested me (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353) but it's stuck on start screen. Therefore I install another one (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967) which is correctly starting.
The thing is that the model is MHL-C09 but I don't remember if the exact region is C33 (FR) or C432 (EU). Does it matter?
Anyway, I downloaded the latest firmware of both versions using Firmware Finder:
MHA-L29C432B369 (8.0.0.369) / MHA-L09C432B369 (8.0.0.369)
MHA-L09C33B317 (8.0.0.317) / MHA-L09BC33B317 (8.0.0.317)
So I boot in TWRP, try to install the Update.zip file of either one of the two versions and ... I still get an error 9.
Apparently it's the following instruction which fails:
Code:
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
See the output log for L09C432B369: https://pastebin.com/1iLNPNBR
Am I doing anything wrong? Is there a missing step?

Gynsu2000 said:
I'm trying to invoke @ante0 as he seems quite an expert
The current situation is the following:
Phone is bootlooping
I can start in fastboot (PHONE Unlocked, FRP Unlock)
I can start on TWRP. I did install the version @ante0 suggested me (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353) but it's stuck on start screen. Therefore I install another one (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967) which is correctly starting.
The thing is that the model is MHL-C09 but I don't remember if the exact region is C33 (FR) or C432 (EU). Does it matter?
Anyway, I downloaded the latest firmware of both versions using Firmware Finder:
MHA-L29C432B369 (8.0.0.369) / MHA-L09C432B369 (8.0.0.369)
MHA-L09C33B317 (8.0.0.317) / MHA-L09BC33B317 (8.0.0.317)
So I boot in TWRP, try to install the Update.zip file of either one of the two versions and ... I still get an error 9.
Apparently it's the following instruction which fails:
Code:
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
See the output log for L09C432B369: https://pastebin.com/1iLNPNBR
Am I doing anything wrong? Is there a missing step?
Click to expand...
Click to collapse
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware

Thanks for the update and the command.
MHA-L09 8.0.0.316(C33)

ante0 said:
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware
Click to expand...
Click to collapse
Thank again for your help.
Follow-up:
I copied the correct ROM version and HuRUpdater however it doesn't work with Blackballs' TWRP.
Code:
********************
* HuRUpdater *
* by zxz0O0 *
********************
Trying to find the gpio-keys event node.
Found and will be using /dev/input/event1!
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/hurupdate-binary
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/busybox
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Archive: /external_sd/fw/MHA-L09C33B316/update.zip
inflating: VERSION.mbn
unzip: invalid zip magic 0447C7F0
CANNOT LINK EXECUTABLE "/tmp/utils/busybox": cannot locate symbol "__sendto_chk" referenced by "/tmp/utils/busybox"...
Aborted
I've tried to switch back to Pretoriano80's twrp but I'm still stuck on startup screen.
Is there any other method? Even downgrading to Nougat would be okay

Gynsu2000 said:
Thank again for your help.
Follow-up:
I copied the correct ROM version and HuRUpdater however it doesn't work with Blackballs' TWRP.
Code:
********************
* HuRUpdater *
* by zxz0O0 *
********************
Trying to find the gpio-keys event node.
Found and will be using /dev/input/event1!
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/hurupdate-binary
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/busybox
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Archive: /external_sd/fw/MHA-L09C33B316/update.zip
inflating: VERSION.mbn
unzip: invalid zip magic 0447C7F0
CANNOT LINK EXECUTABLE "/tmp/utils/busybox": cannot locate symbol "__sendto_chk" referenced by "/tmp/utils/busybox"...
Aborted
I've tried to switch back to Pretoriano80's twrp but I'm still stuck on startup screen.
Is there any other method? Even downgrading to Nougat would be okay
Click to expand...
Click to collapse
I guess you could try:
Extract update.app from update.zip
Download Huawei Update Extractor
Open Huawei Update Extractor and go to options and uncheck header check.
Open update.app in Huawei Update Extractor.
Right click on system and extract selected.
Do the same for vendor.
Flash both using fastboot, then try Pretoriano80s TWRP again.
(you could try to boot phone after flashing system and vendor)
Another solution could be to:
Unpack Pretoriano80s TWRP with Android Image Kitchen, copy ramdisk/sbin/busybox and paste to desktop or somewhere not in the ramdisk folder.
Unpack Blackballs twrp and put the previously copied busybox in ramdisk/sbin/ then repack image and flash.
Then try HuRUpdater again.

For some reason flashing the system worked but not the vendor.
Code:
D:\download\android\mate9\MHA-L09C33B316>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' (460651 KB)...
OKAY [ 10.857s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 10.873s
However, the phone now boots correctly, flashing the system partition was enough (I assume it seems obvious for an experienced guy).
\o/
Thanks a lot @ante0 !

Gynsu2000 said:
For some reason flashing the system worked but not the vendor.
Code:
D:\download\android\mate9\MHA-L09C33B316>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' (460651 KB)...
OKAY [ 10.857s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 10.873s
However, the phone now boots correctly, flashing the system partition was enough (I assume it seems obvious for an experienced guy).
\o/
Thanks a lot @ante0 !
Click to expand...
Click to collapse
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.

ante0 said:
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware
Click to expand...
Click to collapse
Have been able to upgrade latest Oreo firmware using @Blackball twrp.
Just follow the instructions on his page.
1.Now that you have your correct firmware downloaded and intact.
2.Rename to this (update.zip, update_all_hw.zip, update_data_public.zip )
3.Download this file from here https://drive.google.com/file/d/1YM-Bga-wAKOct971WrrKCsX2K3tFP6zF/view?usp=sharing
4.Create a folder and rename to HWOTA8 , copy the downloaded file and the 3 firmware files
5.Now copy the the whole folder to your external storage and boot phone to twrp recovery.
6.Install by locating this file hwota8_update in the HWOTA8 folder on your external storage.
7.When done it will reboot and firmware upgrade processing will take over.
when you use this method,you will not loose and bit of information you original have before the installation,everything will be intact.:good::good:

ante0 said:
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.
Click to expand...
Click to collapse
First thing I checked: bootloader was still unlocked.
Second thing: TWRP -> Backup.
golastic said:
when you use this method,you will not loose and bit of information you original have before the installation,everything will be intact.:good::good:
Click to expand...
Click to collapse
Thanks for the heads up. Hopefully I will backup thing first on TWRP before toying around with the phone.

ante0 said:
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.
Click to expand...
Click to collapse
Ok, so now the phone is correctly starting but I have 2 issues.
First one is more an annoyance than an issue: when I reach the "About" screen, the model pf the phone is marked as ... "Unknown". I've tried to flash in fastboot the correct OEMINFO (using the file from there : https://forum.xda-developers.com/mate-9/development/oeminfo-library-t3555353 ). After that the bootloader was locked and .... I still have an Unknow phone.
Second issue is that I've tried to install superSU but it doesn't seem to work.
Install output is the following:
Code:
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
- System-less mode, boot image support required
- Creating paths
mkdir: can't create directory '/su/bin': File exists
mkdir: can't create directory '/su/xbin': File exists
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sdd35
- Extracting ramdisk
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/dev/block/sdd35] ...
magic: [ANDROID!]
kernel: [12078158] (12079104) @ 0x00080000
ramdisk: [0] (0) @ 0x07c00000
second: [0] (0) @ 0x00f00000
tags: @ 0x07a00000
page size: 2048
unused: [0x00000000] [0x10000125]
dtb(?): [0] (0)
name: []
command line: [loglevel=4 initcall_debug=n page_tracker=on slub_min_objects=16 unmovable_isolate1=2:192M,3:224M,4:256M printktimer=0xfff0a000,0x534,0x538 androidboot.selinux=enforcing buildvariant=user]
extra command line: []
id: [0xe3bfe4262954c0437ae810fc16281a76152117bb000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
- Decompressing ramdisk (none)
- Checking patch status
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Already patched, attempting to find stock backup
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Stock restore failed, attempting ramdisk restore
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Ramdisk restore failed, aborting
umount: can't umount /su: Invalid argument
BusyBox v1.22.1 bionic (2018-01-13 12:03 +0100) multi-call binary.
Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
losetup -d LOOPDEV - disassociate
losetup -a - show status
losetup -f - show next free loop device
-o OFS Start OFS bytes into FILE
-r Read-only
-f Show/use next free loop device
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
- Unmounting /system and /vendor
- Done !
I:Updater process ended with RC=0
I:Install took 8 second(s).
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Updating partition details...
I:Data backup size is 1571MB, free: 51976MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
Full log: https://pastebin.com/QGKdMEPU
I've tried 2 other versions but the result is the same.

Gynsu2000 said:
Ok, so now the phone is correctly starting but I have 2 issues.
First one is more an annoyance than an issue: when I reach the "About" screen, the model pf the phone is marked as ... "Unknown". I've tried to flash in fastboot the correct OEMINFO (using the file from there : https://forum.xda-developers.com/mate-9/development/oeminfo-library-t3555353 ). After that the bootloader was locked and .... I still have an Unknow phone.
Second issue is that I've tried to install superSU but it doesn't seem to work.
Install output is the following:
Code:
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
- System-less mode, boot image support required
- Creating paths
mkdir: can't create directory '/su/bin': File exists
mkdir: can't create directory '/su/xbin': File exists
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sdd35
- Extracting ramdisk
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/dev/block/sdd35] ...
magic: [ANDROID!]
kernel: [12078158] (12079104) @ 0x00080000
ramdisk: [0] (0) @ 0x07c00000
second: [0] (0) @ 0x00f00000
tags: @ 0x07a00000
page size: 2048
unused: [0x00000000] [0x10000125]
dtb(?): [0] (0)
name: []
command line: [loglevel=4 initcall_debug=n page_tracker=on slub_min_objects=16 unmovable_isolate1=2:192M,3:224M,4:256M printktimer=0xfff0a000,0x534,0x538 androidboot.selinux=enforcing buildvariant=user]
extra command line: []
id: [0xe3bfe4262954c0437ae810fc16281a76152117bb000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
- Decompressing ramdisk (none)
- Checking patch status
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Already patched, attempting to find stock backup
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Stock restore failed, attempting ramdisk restore
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Ramdisk restore failed, aborting
umount: can't umount /su: Invalid argument
BusyBox v1.22.1 bionic (2018-01-13 12:03 +0100) multi-call binary.
Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
losetup -d LOOPDEV - disassociate
losetup -a - show status
losetup -f - show next free loop device
-o OFS Start OFS bytes into FILE
-r Read-only
-f Show/use next free loop device
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
- Unmounting /system and /vendor
- Done !
I:Updater process ended with RC=0
I:Install took 8 second(s).
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Updating partition details...
I:Data backup size is 1571MB, free: 51976MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
Full log: https://pastebin.com/QGKdMEPU
I've tried 2 other versions but the result is the same.
Click to expand...
Click to collapse
I would do a full update again, oeminfo won't change model in about. Either using HWOTA as someone posted above or use HuRUpdater
Also, use Magisk instead of supersu. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

In the end I used HWOTA8 and it worked like a charm. Until I discovered that I wasn't able to access a mobile network: SIM card is detected (icon in status bar have it displayed), however I'm not prompted for the sim's pin. First thing I checked was the sim lock using the super code: it's not (SIMLOCK_DEACTIVE). Then I've tried a couple of sims from other carriers but none of them are working.
Unless you guys have an idea, I suppose I should bring it to warranty.

Related

Flashable Filesystem Check and Repair Tool

This flashable script will try to check and fix filesystem errors in your ext and fat32 partitions. The repair on fat32 may not be robust, but at least you will be alerted to any potential issues and can then run a dosfsck/chkdsk to fix issues,
This was created for my SuperNova Rom which uses Data2sd, but can be used for any Rom which uses an ext4 partition.
Potential candidates are phones with new issues of Force closes appearing, which usually signify a partition corruption..
Report on the file system check and repair will be output to /sdcard/repairlog.txt
This could be a "must-have" tool for every sdcard.
[*]Version History
FixFS 21-Sept-11
Initial script
FixFS 0.2 22-Sept-11
More checkpoints in logic
Verbose output

Any followups....

Nice one. If I had a partition to check, I'd definitely use this!

rootSU said:
Nice one. If I had a partition to check, I'd definitely use this!
Click to expand...
Click to collapse
Ha ha..

===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 00:36:27 GMT 2011
Ext4 file system found...
e2fsck running
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
DosFsck running...
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
-----
Above is my result of your awsome tool(thank you so much), seems some errors occured or found problems on my sd, but not fixed during the patch's on.
Would you give me a tip for the next step?
Sent from my HTC Desire using XDA App

You will have to do a manual e2fsck from the shell, since that usually means it is waiting for user intervention due to some errors. Though the automatic options I specified should correct minor issues, some seem to still need intervention
Sent from my HTC Desire using Tapatalk

nice work as per usual matey
ran it once through ROM Manager and your screen in recovery was only visible for a split second, so I checked the repairlog and read this:
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 00:43:51 GMT 2011
Ext4 file system found...
e2fsck running
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
DosFsck running...
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
===================================
When I got home I checked the SD card through windows (no errors) then your script through Max's 4EXT app and no split second reading this time, it read:
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 04:57:43 GMT 2011
Ext4 file system found...
e2fsck running
Your ext4 file system was checked and was clean..No repair was necessary.
Sdcard found..
Attempting to unmount sdcard
DosFsck running...
Your Fat32 file system was checked and was clean..No repair was necessary.
Script has completed operations
So a very big thank you to you and Max

Great tool! Thanks very much, have been looking for something like this for ages.

Hi Droidzone,
something goes wrong for me, i explain it with log below:
recovery.log
Code:
-- Installing: /sdcard/FixFS.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/FixFS.zip
Opening update package...
Installing update...
about to run program [/tmp/pre.sh] with 1 args
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 10:38:42 GMT 2011
Ext4 file system found...
e2fsck running
/tmp/pre.sh: line 56: /tmp/e2fsck: not found
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
umount: can't umount /sdcard: Device or resource busy
DosFsck running...
/tmp/pre.sh: line 86: /tmp/fsck_msdos: not found
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
The log file has been copied to sdcard_repairlog.txt
script result was [|______________________________________________|]
minzip: Extracted file "/tmp/e2fsck"
minzip: Extracted file "/tmp/fsck_msdos"
minzip: Extracted file "/tmp/pre.sh"
________________________________________________
| |
| PARTITION CHECK & REPAIR TOOL |
| ================================== |
| - DROIDZONE - |
| |
| This is an On-Demand Partition Fix tool. |
| If you find too many force closes or freezes |
| on your phone, it may be the first indication|
| of increasing corruption on your ext4 partit-|
| ion. Running this tool will fix most of them.|
| |
| |
| [*]Checking and Fixing File system... |
| [*]Checking Fat32 File system... |
| [*]Checking ext4 File system... |
| [*]Done |
| [*]Repair log in sdcard/repairlog.txt |
|______________________________________________|
Install from sdcard complete.
So, without reboot i connected my adb shell and i'd try manually (with /sdcard alredy unmounted)
Code:
/tmp # ls -ail
ls -ail
213 drwxr-xr-x 2 root root 0 Sep 22 10:38 .
1 drwxr-xr-x 19 root root 0 Sep 22 10:03 ..
722 -rw-rw-rw- 1 root root 10 Sep 22 10:04 4ext_version
721 -rw-rw-rw- 1 root root 3 Sep 22 10:04 batt_level
756 -rwxrwxrwx 1 root root 111492 Aug 1 2008 e2fsck
730 -rw-rw-rw- 1 root root 5 Sep 22 10:04 free_space
757 -rwxr-xr-x 1 root root 22640 Aug 1 2008 fsck_msdos
758 -rwx------ 1 root root 2490 Aug 1 2008 pre.sh
692 -rw-rw-rw- 1 root root 8502 Sep 22 10:49 recovery.log
715 -rw-rw-rw- 1 root root 72 Sep 22 10:03 sd_fstypes
764 -rwxr-xr-x 1 root root 255904 Sep 22 10:38 update_binary
/tmp # /tmp/e2fsck -af /dev/block/mmcblk0p2
/tmp/e2fsck -af /dev/block/mmcblk0p2
/sbin/sh: /tmp/e2fsck: not found
/tmp # /tmp/fsck_msdos -pf /dev/block/mmcblk0p1
/tmp/fsck_msdos -pf /dev/block/mmcblk0p1
/sbin/sh: /tmp/fsck_msdos: not found
/tmp # pre.sh
pre.sh
/sbin/sh: pre.sh: not found
/tmp # ./pre.sh
./pre.sh
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 10:58:36 GMT 2011
Ext4 file system found...
e2fsck running
./pre.sh: line 56: /tmp/e2fsck: not found
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
umount: can't umount /sdcard: Invalid argument
umount: can't forcibly umount /sdcard: Invalid argument
DosFsck running...
./pre.sh: line 86: /tmp/fsck_msdos: not found
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
The log file has been copied to sdcard_repairlog.txt
/tmp # ./tmp/fsck_msdos -pf /dev/block/mmcblk0p1
./tmp/fsck_msdos -pf /dev/block/mmcblk0p1
/sbin/sh: ./tmp/fsck_msdos: not found
i can't understand why ./pre.sh: line 56: /tmp/e2fsck: not found
recovery is kidding me!?
anyway all seems ok using e2fsck built in recovery 4EXT 2.1.3RC4 (i used verbose option):
Code:
~ # e2fsck -afv /dev/block/mmcblk0p2
e2fsck -afv /dev/block/mmcblk0p2
730 inodes used (0.56%)
25 non-contiguous files (3.4%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 720
259347 blocks used (49.47%)
0 bad blocks
0 large files
707 regular files
14 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
721 files

Weird indeed that the files in /tmp cant be accessed. Anyway, I'll add code to abort script if the binaries cant be found..it doesnt look good with the script saying everything's working.. I didnt add verbose early because of the output (confuses newbies?), but I'll add it too.
Edit: Forgot to mention that I use 4ext too, and no such issues here.

Droidzone said:
Weird indeed that the files in /tmp cant be accessed
Click to expand...
Click to collapse
nope, file can be accessed! with cat /tmp/e2fsck i see correct output
Droidzone said:
I'll add code to abort script if the binaries cant be found..it doesnt look good with the script saying everything's working..
Click to expand...
Click to collapse
+1 lol
did you try with 4EXT 2.1.3RC4 too?

Droidzone said:
You will have to do a manual e2fsck from the shell, since that usually means it is waiting for user intervention due to some errors. Though the automatic options I specified should correct minor issues, some seem to still need intervention
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Really appreciate for your kind explanation ^^;
Then, could somebody inform me how to to do a manual e2fsck from the shell or any links shows relative information? I've already questioned it at Q & A, but so far nobody has answered...

limscap1 said:
Really appreciate for your kind explanation ^^;
Then, could somebody inform me how to to do a manual e2fsck from the shell or any links shows relative information? I've already questioned it at Q & A, but so far nobody has answered...
Click to expand...
Click to collapse
It was there in Ultrakiller's quote.
Code:
e2fsck -afv /dev/block/mmcblk0p2
The command is found in /system/bin usually..My flasher also copies that file to /tmp. So:
Code:
chmod 755 /tmp/e2fsck
/tmp/e2fsck -afv /dev/block/mmcblk0p2

I would be linked in first post, for all that users who can't use the droidzone's script.
Reboot in Recovery, and connect adb shell.
EXT4 REPAIR/CHECK
Code:
e2fsck -afv /dev/block/mmcblk0p2
e2fsck will check and repair ext4 partition if needed.
an example:
Code:
e2fsck -afv /dev/block/mmcblk0p2
730 inodes used (0.56%)
25 non-contiguous files (3.4%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 720
259347 blocks used (49.47%)
0 bad blocks
0 large files
707 regular files
14 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
721 files
FAT32 REPAIR/CHECK
mount usb partition on pc using recovery menu.
Once connected usb cable and opened cmd on pc type:
Code:
chkdsk /R f:\
in my case fat32 partition is f:
chkdsk can take a while (around 20min)
an example of output here (sorry, italian OS, anyway in my case no errors found)
Code:
Il file system è di tipo FAT32.
Numero di serie del volume: B996-8582
Verifica dei file e delle cartelle in corso...
Verifica dei file e delle cartelle completata.
Verifica dello spazio disponibile in corso...
Verifica dello spazio disponibile completata.
Verifica del file system effettuata. Nessun problema rilevato.
13.525.072 KB di spazio totale su disco.
2.408 KB in 295 cartelle.
6.963.592 KB in 1.891 file.
6.559.064 KB disponibili.
8.192 byte in ogni unità di allocazione.
1.690.634 unità totali di allocazione su disco.
819.883 unità di allocazione disponibili su disco.
If i helped someone please hit thanks button!

First of all, thanks Droidzone for your work
I have run the tool and had this
e2fsck running
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
DosFsck running...
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
-----
Click to expand...
Click to collapse
When running e2fsck from adb doesn't find anything wrong:
(sorry can't copy/paste, I have attached an image)
And if I run a script (founded in a MIUI rom, a didn't remember what version) from gscript, called check sd it says:
Will be Check your SD Card from kernel message:
===============================================
[ 19.726623] mmcblk0: mmc1:b368 USD 7.46 GiB
[ 19.727478] mmcblk0: p1 p2 p3
[ 20.836303] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
[ 24.104003] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
[ 24.484558] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
[ 26.537750] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
===============================================
If you found error between two lines, then your SD card is broken.
Click to expand...
Click to collapse
The commands on that script are:
mkdir /sdcard/gscript/resources>/dev/null
clear
echo "echo Will be Check your SD Card from kernel message:" > /sdcard/gscript/resources/temp.sh
echo "echo ===============================================" >> /sdcard/gscript/resources/temp.sh
echo "dmesg|grep mmcblk0" >> /sdcard/gscript/resources/temp.sh
echo "echo ===============================================" >> /sdcard/gscript/resources/temp.sh
echo "echo If you found error between two lines, then your SD card is broken." >>/sdcard/gscript/resources/temp.sh
su</sdcard/gscript/resources/temp.sh
rm /sdcard/gscript/resources/temp.sh
Click to expand...
Click to collapse
If someone can help, I'll be really grateful. I have also tried repartitioning the whole SD card with gparted, but the problem still appears. I'm using Alex-V ROM d2ext with default kernel (snq-)
Thanks in advance

blackhawk_LA said:
First of all, thanks Droidzone for your work
I have run the tool and had this
When running e2fsck from adb doesn't find anything wrong:
(sorry can't copy/paste, I have attached an image)
And if I run a script (founded in a MIUI rom, a didn't remember what version) from gscript, called check sd it says:
The commands on that script are:
If someone can help, I'll be really grateful. I have also tried repartitioning the whole SD card with gparted, but the problem still appears. I'm using Alex-V ROM d2ext with default kernel (snq-)
Thanks in advance
Click to expand...
Click to collapse
That check in Miui seems to be at the kernel level..However imho I dont see an error...that line just seems to be the kernel output saying what ext4 options have been used for the mount (should be present for everyone ). Do you see any actual issues while using the card?

I haven't see any big issues, just noticed that the sdext restore from a nandroid seemed to take too much time (7-8 minutes for just 300mb) and that's why i used your tool and have a look at this post.
But everything is working fine (or it seems so), just wanted to know if my files could be starting to get corrupted or something.
Thanks

As far as my script is concerned..it depends on error code from e2fsck to report file system state. That particular error code means that a standard error level was not returned, so only a command line manual e2fsck will show exactly what was the system response. See Post #14 for how to do that.

Mmm this is what I did, I think. See the attached image in my other message; it seems there was no erros (0 bad blocks)

Hi, got an error in clockwork recovery : error in fixfsv0.2.zip ( status 0 ) installation aborted ..
any clues ?

mounting error /cache /system

Hey Guys,
Just flashed Kisadworx 2.6.1, which is by the way, an awesome rom.... But i experienced some problems while flashing... i got some errors when wiping cache, and dalvik cache because they couldn't get mounted right... but as i had some problems earlier with kyrillos 9.7 and fugumod i assumed it would be ok, and everything seems to be working nicely...
today i wanted to reinstall a backup via titanium and suddenly my phone rebooted...
i went to /res and found this in pre-init.log
Code:
Fugumod - GT-I5800 version : 2.4.beta3
Linux (none) 2.6.32.9 #fugumod_v2.4.beta3_standard Fri May 20 04:39:17 CEST 2011 armv6l GNU/Linux
Build fs_current
fsck filesystems
/dev/block/mmcblk0p2: clean, 75/62496 files, 40118/249961 blocks
umount: can't umount /sdcard: No such file or directory
umount: can't umount /cache: No such file or directory
umount: can't umount /system: Invalid argument
umount: can't umount /data: No such file or directory
rm: can't remove '/fugumod_sd/fugumod_data.tar': No such file or directory
STL6 : rfs
STL7 : rfs
STL8 : rfs
MMC : ext4
in user.log
Code:
Wed Mar 6 15:32:54 UTC 2013 USER EARLY INIT START
Wed Mar 6 15:32:55 UTC 2013 USER EARLY INIT DONE
Wed Mar 6 15:32:55 UTC 2013 USER INIT START
START 'S97BulletProof_Apps'
EXIT 'S97BulletProof_Apps' (0)
START 'SS99SuperCharger'
EXIT 'SS99SuperCharger' (69)
START 'S_01sysctl'
vm.dirty_writeback_centisecs = 1000
vm.dirty_expire_centisecs = 500
EXIT 'S_01sysctl' (0)
START 'S_05app2sd'
mkdir: can't create directory '/data/misc': File exists
mkdir: can't create directory '/data/misc/app2sd': File exists
mkdir: can't create directory '/system/sd': File exists
ln: /etc/mtab: File exists
mkdir: can't create directory '/system/sd/log': File exists
mkdir: can't create directory '/system/sd/app': File exists
mkdir: can't create directory '/system/sd/dalvik-cache': File exists
EXIT 'S_05app2sd' (0)
START 'S_15perms'
EXIT 'S_15perms' (0)
START 'S_20performance'
EXIT 'S_20performance' (0)
START 'S_99complete'
EXIT 'S_99complete' (0)
Wed Mar 6 15:33:06 UTC 2013 USER INIT DONE
============> 1
and in fugumod.log
Code:
Checking mmcblk0p2
/dev/block/mmcblk0p2: clean, 75/62496 files, 40118/249961 blocks
Checking stl6
rfs, not checking
Checking stl7
rfs, not checking
Checking stl8
rfs, not checking
do i have to worry about something not working? pre-init.log doesn't seem to healthy...
somebody else got the same problems or at least knows why this issue is appearing?
Thanks in advance

Try install g3mod
Sent from my GT-I5800 using xda app-developers app

is this a known issue of kisadworx rom or fugumod? i read that kisadworx rom has also issues with generating the md5 sum while doing a nandroid backup... and as fugumod has rfs-filesystems will it work with g3mod? i thought they were only using ext-filesystems?1

[Q] HELP stuck in a serious bootloop

My htc was off for one month because i went to a trip and did not take it with me. when i came back i turned it on and boom! bootloop! came from nowhere.
I had the vipers rom on it so i tried to update to the newest vipers rom but still bootloop. i tried to install different rom but nothing help,
At the end i installed RUU and still i'm in bootloop! please help me

amitshkuri said:
My htc was off for one month because i went to a trip and did not take it with me. when i came back i turned it on and boom! bootloop! came from nowhere.
I had the vipers rom on it so i tried to update to the newest vipers rom but still bootloop. i tried to install different rom but nothing help,
At the end i installed RUU and still i'm in bootloop! please help me
Click to expand...
Click to collapse
can you boot into bootloader?
if yes post all the on screen details

rzr86 said:
can you boot into bootloader?
if yes post all the on screen details
Click to expand...
Click to collapse
yes i can get into bootloader but in recovery i get error.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
JAN 13 2012, 17:33:34
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

amitshkuri said:
yes i can get into bootloader but in recovery i get error.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
JAN 13 2012, 17:33:34
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
from this guide it has 3 options to flash 4ext recovery(see step 1)
http://forum.xda-developers.com/showthread.php?t=1472298
after that go into recovery
format all partitions except sdcard
flash the rom
see if it boots

rzr86 said:
from this guide it has 3 options to flash 4ext recovery(see step 1)
http://forum.xda-developers.com/showthread.php?t=1472298
after that go into recovery
format all partitions except sdcard
flash the rom
see if it boots
Click to expand...
Click to collapse
i flashed 4ext recovery and flashed 3.33 firmware and flashed ARHD 7.2 (i did full wipe for all patitions)
still in bootloop but now it pass the HTC logo and the quitly brilliant logo and start the beats animation then it restart.

HI
GREETINGS
according to your bootloader you have stock htc hboot and
stock htc hboot does not go well with soff
flash the hboot in my attachment
to flash the hboot:-
1 put the file in root of sd card
2 reboot into bootloader
3 the bootloader will scan the file, follow on screen instruction
4 reboot back in to bootloader and make a clean installation of the rom as suggested by "RZR86"

shrex said:
HI
GREETINGS
according to your bootloader you have stock htc hboot and
stock htc hboot does not go well with soff
flash the hboot in my attachment
to flash the hboot:-
1 put the file in root of sd card
2 reboot into bootloader
3 the bootloader will scan the file, follow on screen instruction
4 reboot back in to bootloader and make a clean installation of the rom as suggested by "RZR86"
Click to expand...
Click to collapse
I flashed the new hboot and flashed the recovery again and made a clean installation including format for all partitions and still i stuck in this bootloop! what can i do more?

amitshkuri said:
what can i do more?
Click to expand...
Click to collapse
Absolutely loads of stuff. First thing is to get the logs.
Flash a rom with adb set in the default.prop in the boot image ramdisk ( CM for example )
while the device is bootlooping run
Code:
adb shell dmesg
which gives the kernel messages then you can run
Code:
adb logcat -b system -b radio -b events -b main
this will run forever, you'll notice it repeating the same messages over and over, look out for lines that start with "E/"
they're errors being reported and will lead you to the cause of you're bootloop
If either of these two fail then reboot into recovery and run
Code:
adb shell cat /dev/last_kmsg
This is a saved copy of dmsg from the last session.
Once you've got the logs you can easily pinpoint the cause of the problem all you got is read them
PROTIP: Look for the word error or fail or something similar

ok so that's all the errors i found while booting:
E/QC-NETMGR-LIB( 165): couldn't open file /sys/module/f_rmnet/parameters/rmnet_ctl_ch
E/QC-NETMGR-LIB( 165): couldn't open /sys/module/rmnet/parameters/rmnet_ctl_ch
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/DxDrmNexPlayerIntegrator( 169): ** Discretix Server loaded config file - result=0 **
E/DxDrmNexPlayerIntegrator( 169): ** Discretix SignalsListener Thread is starting **
E/DxSecureClock( 169): ** Discretix Clock Monitor is starting **
E/msm8660.gralloc( 153): DEBUG_CALC_FPS: 0
E/msm8660.gralloc( 153): period: 10
E/msm8660.gralloc( 153): ignorethresh_us: 500000
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 0
E/SurfaceFlinger( 153): composer device failed to initialize (Invalid argument)
E/rmt_storage( 120): Unable to open /boot/modem_fsg
E/rmt_storage( 120): Invalid rmt_storage client
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 1
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 2
E/HtcBootAnimation( 225): Could not find width.
E/HtcBootAnimation( 225): Could not find height.
E/HtcBootAnimation( 225): Could not find framerate.
E/HtcBootAnimation( 225): Could not find part1.
E/HtcBootAnimation( 225): Could not find part2.
E/HtcBootAnimation( 225): Could not find part3.
E/HtcBootAnimation( 225): sqlite3_open error, sqlite result: 14, errno: 2, No such file or directory
E/QC-DIAG_LSM( 156):
E/QC-DIAG_LSM( 156): Diag_LSM: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 3
E/ExtendedExtractor( 156): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: reloc_library[1290]: 156
E/AudioPolicyManagerBase( 156): Could not open support_receiver()
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 4
And this came at the second of crash:
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 5
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 6
E/QC-NETMGR-LIB( 165): ifioctl: close port failed: (9)Bad file number
E/QC-NETMGR-LIB( 165): ifioctl: open port failed: (19)No such device
E/QC-NETMGR-LIB( 165): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 7
am i in trouble?

amitshkuri said:
am i in trouble?
Click to expand...
Click to collapse
It's difficult to say with ONLY the errors LOL. You've just removed all the context of what was going on around leading upto it. Can you post the rest of them, not here though, pastebin or somewhere like that.
Also dmesg output would be pretty useful to see if all the drivers are install correctly.
At first glance, You seem to be missing some vital libraries. files, to say anything more at this point would just be guessing? but yeah, dmesg and a full logcat.
Actually to save a back and forth you can run the following commands
Code:
adb root
adb shell stop
adb shell dumpstate > state.txt
adb shell dumpsys > sys.txt
Don't know what you know so I'll explain what this does.
adb root , restarts adb as the root user
adb shell stop, this stops the servicemanager and it's child services , basically stop loading android. If you have a boot animation you should see it stop, this also stops device from rebooting as the next commands take some time to run.
dumpstate and dumpsys will dump your entire device contents to state.txt and sys.txt on your desktop machine. you won't see any output and they do take some time to run so please be patient. As you've fully formatted it I wouldn't expect any personal data to be present in those files but may contain device specific info please have a look before posting. searching the for things like your email address, name, IMEI, serial no's etc should help.
Then zip the files and attach them to this thread. Like I mentioned these files contain everything about the Device and the current state and will give us everything we need to figure out whats wrong.
If you're not comfortable "doing the dump!" ( sounds like a song ) then option 1 of logcat and dmesg should do I'll probably end up asking for more but meh!

ok i tried but
Code:
adb root
adb shell stop
didn't help and the boot restart again and again so i cannot write the rest of codes you gave me.
i attached a rar file with the context of logcat and dmesg.

amitshkuri said:
ok i tried but
Code:
adb root
adb shell stop
didn't help and the boot restart again and again so i cannot write the rest of codes you gave me.
i attached a rar file with the context of logcat and dmesg.
Click to expand...
Click to collapse
That's fine dmesg tells all in this case, It's a bit weird. you system partition seem to be at fault. these messages
Code:
<6>[ 2.457794] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly filesystem
<6>[ 2.457977] EXT4-fs (mmcblk0p22): write access will be enabled during recovery
<6>[ 2.466827] EXT4-fs (mmcblk0p22): barriers disabled
<6>[ 2.468963] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.476013] EXT4-fs (mmcblk0p22): mounted filesystem with writeback data mode. Opts: barrier=0
which is just information but a couple of lines down is this
Code:
<6>[ 3.588012] EXT4-fs (mmcblk0p22): re-mounted. Opts: noauto_da_alloc,barrier=0
Logcat also has this related message
Code:
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): The needs_recovery flag is set. Please run e2fsck before clearing
what it looks like is happening is the kernel has remounted your /system partition to try to set it up for recovery while the device is booting make system files unavailable in the process, which ties up to the messages about missing libraries from earlier on. it may well be easily solved simply by following the instruction and running e2fsck on /dev/block/mmcblk0p22, it worth a shot I'd say.
reboot into recovery and run
Code:
adb shell e2fsck /dev/block/mmcblk0p22
you may also have to remove the need_recovery flag from the partition... I don't know how to do that off the top of my head and I have to go out for a bit.... Google may be your friend
More Soon!

own diBeco
trevd said:
That's fine dmesg tells all in this case, It's a bit weird. you system partition seem to be at fault. these messages
Code:
<6>[ 2.457794] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly filesystem
<6>[ 2.457977] EXT4-fs (mmcblk0p22): write access will be enabled during recovery
<6>[ 2.466827] EXT4-fs (mmcblk0p22): barriers disabled
<6>[ 2.468963] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.476013] EXT4-fs (mmcblk0p22): mounted filesystem with writeback data mode. Opts: barrier=0
which is just information but a couple of lines down is this
Code:
<6>[ 3.588012] EXT4-fs (mmcblk0p22): re-mounted. Opts: noauto_da_alloc,barrier=0
Logcat also has this related message
Code:
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): tune2fs 1.41.12 (17-May-2010)
I//system/xbin/busybox( 107): The needs_recovery flag is set. Please run e2fsck before clearing
what it looks like is happening is the kernel has remounted your /system partition to try to set it up for recovery while the device is booting make system files unavailable in the process, which ties up to the messages about missing libraries from earlier on. it may well be easily solved simply by following the instruction and running e2fsck on /dev/block/mmcblk0p22, it worth a shot I'd say.
reboot into recovery and run
Code:
adb shell e2fsck /dev/block/mmcblk0p22
you may also have to remove the need_recovery flag from the partition... I don't know how to do that off the top of my head and I have to go out for a bit.... Google may be your friend
More Soon!
Click to expand...
Click to collapse
The shell e2fsck did not help, still in bootloop.
i searched in google about the need_recovery flag and i found one post that explain how to do this but in ubuntu linux
the command " debugfs " mentioned there, i dont really understand what to do.

amitshkuri said:
The shell e2fsck did not help, still in bootloop.
i searched in google about the need_recovery flag and i found one post that explain how to do this but in ubuntu linux
the command " debugfs " mentioned there, i dont really understand what to do.
Click to expand...
Click to collapse
hi again.
After reading some more e2fsck need some extra options. apologises for that
Also as is usually the case with these things you're not the first person to have this problem. A quick xda search for "The needs_recovery flag is set" brings up this post
I've just tested it because my cache partition has the needs_recovery flag set so I ran the commands in that post in recovery and it did clear the needs_recovery flag. so in your case you need to boot into recovery make sure /system is NOT mount which should be the default state and run the following commands
Code:
adb shell
tune2fs -l /dev/block/mmcblk0p22 | grep features
this command get the list of filesystem features it should look something like this ( order may be different )
Code:
Filesystem features: has_journal resize_inode filetype needs_recovery extent sparse_super large_file
Next we'll run e2fsck with the right command this time LOL
Code:
e2fsck -f /dev/block/mmcblk0p22
After that we can remove the old journal with tune2fs
Code:
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
This should remove both the has_journal and needs_recovery flags from the feature list. Seeing as has_journal was set we'll turn it back on
Code:
tune2fs -O has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
Note the caret symbol ( ^ ) which is the difference between the above to commands. This controls whether a feature should be added or removed
Finally check the feature list again
Code:
tune2fs -l /dev/block/mmcblk0p22 | grep features
It should now look like this or something similar, If it still has needs_recovery in the list then something is wrong
Code:
Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
All we need to do now is pray to the ghost of steve jobs and say the magic words
Code:
reboot
And hopefully we might have a win for you! :good:

when i write this line: e2fsck -f /dev/block/mmcblk0p22
i get this: Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>?
if i press "y" i get this: Inode 13765 is in use, but has dtime set. Fix<y>?
and more and more and more questions and cant continue with the next lines you gave me.
what to do?

amitshkuri said:
when i write this line: e2fsck -f /dev/block/mmcblk0p22
i get this: Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>?
if i press "y" i get this: Inode 13765 is in use, but has dtime set. Fix<y>?
and more and more and more questions and cant continue with the next lines you gave me.
what to do?
Click to expand...
Click to collapse
e2fsck -f -y /dev/block/mmcblk0p22
That will answer yes to all questions!

i did all exactly and still in a bootloop..
i got Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
without the needs recovery, all went well.
is there hope?

amitshkuri said:
i did all exactly and still in a bootloop..
i got Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
without the needs recovery, all went well.
is there hope?
Click to expand...
Click to collapse
Time to rinse and repeat, Grab the dmesg and the logcat and lets see what it's saying now? Also Have you tried reflashing the rom, it's possible the tune2fs has deleted some files but we can only find out by looking at the logs!

i tried now to reflashed and still bootloop :/
i attached the new demsg and logcat.
thank you for all the help!

amitshkuri said:
i tried now to reflashed and still bootloop :/
i attached the new demsg and logcat.
thank you for all the help!
Click to expand...
Click to collapse
Not a problem on the help. At least you bought an interesting problem to solve It's not your normal bootloop cause.
hmmm , It seems to have gone back to needs recovery.... Ok. Can you run the command from earlier but this time do not re-add the journal feature, so these commands
Code:
tune2fs -l /dev/block/mmcblk0p22 | grep features
e2fsck -f -y -v /dev/block/mmcblk0p22
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p22
tune2fs -l /dev/block/mmcblk0p22 | grep features
#EDIT Mount as read only to mark it ready for mounting
mount -ro -text4 /dev/block/mmcblk0p22 /system
reboot
can you copy the output of these commands and post them up, I'm just curious to see what its runnning.
Do you know how to make your boot image insecure and how to mount /system with rw by default?
If not can you send me the boot image you're using an i'll fix it up.
The plan is to attempt the fs repair and remove journaling which from what I understand can be responsible for triggering the needs_recovery. should that not work, the kernel will try running recovery on the fs at boot time but this time it won't need to remount the /system partition because it will be already mounted as rw ... that's the theory at least.
If it fails send the logs and we'll have a look a some other options depending on the log out. But I wouldn't be worried there's still a couple of more things we can leverage to fixup the system partition.

unable to update CM-13.0-NIGHTLY[otus] to CM-14.1-NIGHTLY [otus] in Moto E 2015.

iam getting the below specified error while updating the Rom cm-13.0- NIGHTLY-otus to cm-14.1-20161216-NIGHTLY-otus on Motorola E 2015 3G.
i tried update it via recovery and cm updater but getting same error..
i got this error :
Installing '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Target: 1481879506
Target: 1481879506
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
unmount of /system failed; no such volume
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...
performing update
open "/dev/block/bootdevice/by-name/system" failed: No such file or directory
script aborted: E1001: Failed to update system image.
Patching system image unconditionally...
E1001: Failed to update system image.
E:unknown command [log]
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.zip'
E:Error installing zip file '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.zip'
Done processing script file
any help.. Thanx

E:Unable to unlock /dev/block/mmcblk0* for flashing: (null)

DEVICE: samsung galaxy f22 sm-e225f (2022)
ANDROID VERSION: 11
TWRP: UNOFFICAL TWRP 3.6.11
VBMETA: disabled
MAGISK INSTALLED before flashing TWRP and flashing using TWRP
Iperation_start: 'Flashing'
Installing zip file '/external_sd/v4afx_v2.7.2.1.zip'
Unmounting System...
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
- Mounting /system
mount: mounting /system on /system_root failed: Invalid argument
- Mounting /system_root
- Mounting /vendor
- Device is system-as-root
- Mounting /apex/com.android.apex.cts.shim
- Mounting /apex/com.android.art
- Mounting /apex/com.android.i18n
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.vndk.v30
- Mounting /apex/com.android.wifi
- Mounting /apex/com.android.adbd
- Mounting /apex/com.android.cellbroadcast
- Mounting /apex/com.android.conscrypt
- Mounting /apex/com.android.extservices
- Mounting /apex/com.android.ipsec
- Mounting /apex/com.android.media
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.mediaprovider
- Mounting /apex/com.android.neuralnetworks
- Mounting /apex/com.android.os.statsd
- Mounting /apex/com.android.permission
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.sdkext
- Mounting /apex/com.android.tethering
- Mounting /apex/com.android.tzdata
Archive: /external_sd/v4afx_v2.7.2.1.zip
inflating: module.prop
***********************************************************
ViPER4Android FX
by ViPER520, ZhuHang, Pittvandewitt, MrWhite214, Zackptg5
***********************************************************
*******************
Powered by Magisk
*******************
Archive: /external_sd/v4afx_v2.7.2.1.zip
inflating: customize.sh
**************************************
* MMT Extended by Zackptg5 @ XDA *
**************************************
- Only uninstall is supported in recovery
Uninstalling!
- Unmounting partitions
I:Updater process ended with RC=0
I:Install took 10 second(s).
E:Unable to unlock /dev/block/mmcblk0p4 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p6 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p14 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p13 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p9 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p18 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p15 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p7 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p5 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p11 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p8 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p10 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0boot0 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p12 for flashing: (null)
Updating partition details...
I:checking for twrp app
Iata backup size is 10663MB, free: 96262MB.
...done
I:Set page: 'flash_done'
Iperation_end - status=0
I:Set page: 'clear_vars'
TRIED:
mount -o rw /dev/block/mmcblk0p42
mount -o rw /dev/block/mmcblk0p14
mount -o rw /dev/block/mmcblk0boot0
ERROR: mount: '/dev/block/mmcblk014' not in fstab
factory reset
wiping data, internal storage, cache, dalvik_cache
[ EDIT: I flashed self-modified nethunter kernel twrp-only flashable zip. And the errors are the same. The flashing shows successful, then those errors pop up. Device boots up normally, and kernel shows "4.14.186-nethunter". I am worried if the flashing didn't correctly succeed. ]

README.md
Code:
## Flash in Magisk Manager ONLY

aIecxs said:
README.md
Code:
## Flash in Magisk Manager ONLY
Click to expand...
Click to collapse
It was an example. I flashed self-modified nethunter kernel twrp-only flashable zip. and the errors are the same. the flashing shows successful, then those errors pop up. device boots up normally, and kernel shows "4.14.186-nethunter". i am worried if the flashing didn't correctly succeed.

So what's the question here? You don't know what the error means?
Code:
LOGERR("Unable to unlock %s for flashing: %s\n", block_device.c_str());
Does your device have mmcblk0 emmc flash memory at all, sure it's not your MicroSD Card?
MediaTek Helio G80 (MT6769V/CU) looks like support both eMMC 5.1 and UFS 2.1
https://www.gsmarena.com/compare.php3?&idPhone1=10996&idPhone2=10948&idPhone3=10429

aIecxs said:
So what's the question here? You don't know what the error means?
Code:
LOGERR("Unable to unlock %s for flashing: %s\n", block_device.c_str());
Does your device have mmcblk0 emmc flash memory at all, sure it's not your MicroSD Card?
MediaTek Helio G80 (MT6769V/CU) looks like support both eMMC 5.1 and UFS 2.1
https://www.gsmarena.com/compare.php3?&idPhone1=10996&idPhone2=10948&idPhone3=10429
Click to expand...
Click to collapse
the question is the flashing shows successful when there are errors. what does the error mean and did my kernel install correctly?

you are the creator of that flashable zip, only you can know what you're doing.
all I can see from the incomplete log you provided you're trying to install v4afx_v2.7.2.1.zip from TWRP regardless it must flashed from Magisk. you said this is just example, so I am not spending time in analyzing v4afx_v2.7.2.1.zip and figuring out what it does.
if you get similar error about Unable to unlock mmcblk0 for flashing for each and every flashable zip, it's probably not an issue with the zip itself.
the error means some operation was unable to unlock partition for flashing. it's lacking context, so you should provide recovery.log at least

aIecxs said:
you are the creator of that flashable zip, only you can know what you're doing.
all I can see from the incomplete log you provided you're trying to install v4afx_v2.7.2.1.zip from TWRP regardless it must flashed from Magisk. you said this is just example, so I am not spending time in analyzing v4afx_v2.7.2.1.zip and figuring out what it does.
if you get similar error about Unable to unlock mmcblk0 for flashing for each and every flashable zip, it's probably not an issue with the zip itself.
the error means some operation was unable to unlock partition for flashing. it's lacking context, so you should provide recovery.log at least
Click to expand...
Click to collapse
twrp log and dmesg log

regarding kernel:
that one failed, probably because (1) device is dynamic partitions read-only, or (2) script is not handling /system_root/system correctly
Code:
- Target Image: /dev/block/mmcblk0p36
- Copying firmware to /system/etc/firmware
that part succeed, unrelated to the below error messages
Code:
- Flashed new bootimage
- Boot image patching complete
This looks like a bug in TWRP, please claim it to TWRP maintainer, or just ignore it
Code:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)

aIecxs said:
regarding kernel:
that one failed, probably because (1) device is dynamic partitions read-only, or (2) script is not handling /system_root/system correctly
Code:
- Target Image: /dev/block/mmcblk0p36
- Copying firmware to /system/etc/firmware
that part succeed, unrelated to the below error messages
Code:
- Flashed new bootimage
- Boot image patching complete
This looks like a bug in TWRP, please claim it to TWRP maintainer, or just ignore it
Code:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
Click to expand...
Click to collapse
Code:
---Magisk Logs---
24.3 (24300)
05-23 09:38:42.264 602 602 I : Magisk 24.3(24300) daemon started
05-23 09:38:42.265 602 602 I : * Device API level: 30
05-23 09:38:42.275 602 604 I : ** post-fs-data mode running
05-23 09:38:42.275 602 604 E : unlock mmcblk0p42 failed with 13: Permission denied
05-23 09:38:42.276 602 604 E : unlock mmcblk0p11 failed with 13: Permission denied
05-23 09:38:42.276 602 604 E : unlock mmcblk0p4 failed with 13: Permission denied
05-23 09:38:42.277 602 604 E : unlock mmcblk0p18 failed with 13: Permission denied
05-23 09:38:42.277 602 604 E : unlock mmcblk0p6 failed with 13: Permission denied
05-23 09:38:42.278 602 604 E : unlock mmcblk0boot0 failed with 13: Permission denied
05-23 09:38:42.278 602 604 E : unlock mmcblk0p15 failed with 13: Permission denied
05-23 09:38:42.279 602 604 E : unlock mmcblk0p5 failed with 13: Permission denied
05-23 09:38:42.279 602 604 E : unlock mmcblk0p7 failed with 13: Permission denied
05-23 09:38:42.279 602 604 E : unlock mmcblk0p14 failed with 13: Permission denied
05-23 09:38:42.279 602 604 E : unlock mmcblk0p10 failed with 13: Permission denied
05-23 09:38:42.280 602 604 E : unlock mmcblk0p8 failed with 13: Permission denied
05-23 09:38:42.280 602 604 E : unlock mmcblk0p13 failed with 13: Permission denied
05-23 09:38:42.286 602 604 E : unlock mmcblk0 failed with 13: Permission denied
05-23 09:38:42.292 602 604 E : unlock mmcblk0p12 failed with 13: Permission denied
05-23 09:38:42.292 602 604 E : unlock mmcblk0p9 failed with 13: Permission denied
05-23 09:38:42.297 602 604 I : * Mounting mirrors
05-23 09:38:42.297 602 604 I : link: /dev/hmrL/.magisk/mirror/metadata
05-23 09:38:42.297 602 604 I : mount: /dev/hmrL/.magisk/mirror/vendor
05-23 09:38:42.297 602 604 I : mount: /dev/hmrL/.magisk/mirror/product
05-23 09:38:42.297 602 604 I : link: /dev/hmrL/.magisk/mirror/cache
05-23 09:38:42.297 602 604 I : mount: /dev/hmrL/.magisk/mirror/data
05-23 09:38:42.297 602 604 I : link: /dev/hmrL/.magisk/mirror/system
05-23 09:38:42.297 602 604 I : mount: /dev/hmrL/.magisk/mirror/system_root
05-23 09:38:42.297 602 604 I : link: /dev/hmrL/.magisk/mirror/system_ext
05-23 09:38:42.297 602 604 I : * Initializing Magisk environment
05-23 09:38:42.350 602 604 I : * Running post-fs-data.d scripts
05-23 09:38:42.353 602 604 I : * Running module post-fs-data scripts
05-23 09:38:42.353 602 604 I : * Loading modules
05-23 15:23:43.917 602 604 I : ** late_start service mode running
05-23 15:23:43.917 602 604 I : * Running service.d scripts
05-23 15:23:43.917 602 604 I : * Running module service scripts
05-23 15:24:05.509 602 604 I : ** boot_complete triggered
---Manager Logs---
24.3 (24300)

aIecxs said:
regarding kernel:
that one failed, probably because (1) device is dynamic partitions read-only, or (2) script is not handling /system_root/system correctly
Code:
- Target Image: /dev/block/mmcblk0p36
- Copying firmware to /system/etc/firmware
that part succeed, unrelated to the below error messages
Code:
- Flashed new bootimage
- Boot image patching complete
This looks like a bug in TWRP, please claim it to TWRP maintainer, or just ignore it
Code:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
Click to expand...
Click to collapse
During flahing of magisk.zip in twrp it showed same errors but magisk is installed successfully. If it's a bug in twrp, do i need to worry about it?
twrp maintainer is not responding

please take a look if you want full log. Thank you

this is the kernel i've managed to flash successfully but with errors demonstrated above, which is completely out of my comprehension. Can you check it for errors? any help will be greatly appreciated.

that error is in Magisk for same partitions as in TWRP, therefore it's not a bug in TWRP. maybe it's not even an error at all, can be ignored
Code:
E : unlock mmcblk0p42 failed with 13: Permission denied
E : unlock mmcblk0p11 failed with 13: Permission denied
E : unlock mmcblk0p4 failed with 13: Permission denied
E : unlock mmcblk0p18 failed with 13: Permission denied
E : unlock mmcblk0p6 failed with 13: Permission denied
E : unlock mmcblk0boot0 failed with 13: Permission denied
E : unlock mmcblk0p15 failed with 13: Permission denied
E : unlock mmcblk0p5 failed with 13: Permission denied
E : unlock mmcblk0p7 failed with 13: Permission denied
E : unlock mmcblk0p14 failed with 13: Permission denied
E : unlock mmcblk0p10 failed with 13: Permission denied
E : unlock mmcblk0p8 failed with 13: Permission denied
E : unlock mmcblk0p13 failed with 13: Permission denied
E : unlock mmcblk0 failed with 13: Permission denied
E : unlock mmcblk0p12 failed with 13: Permission denied
E : unlock mmcblk0p9 failed with 13: Permission denied

fermi6-626 said:
this is the kernel i've managed to flash successfully but with errors demonstrated above, which is completely out of my comprehension. Can you check it for errors? any help will be greatly appreciated.
Click to expand...
Click to collapse
regarding /system/etc/firmware
you are using anykernel wrong, I think it should be $SYSTEM/etc/firmware at least (not sure about the read-only ext4-dedup/logical partitions, though)
maybe @osm0sis will help you out
edit: unrelated to anykernel

aIecxs said:
regarding /system/etc/firmware
you are using anykernel wrong, I think it should be $SYSTEM/etc/firmware at least (not sure about the read-only ext4-dedup/logical partitions, though)
maybe @osm0sis will help you out
Click to expand...
Click to collapse
Because I don't know how to use it. I left it the way it was modified by nethunter-kernel-builder. May be it is a samsung device's problem? If so how do I mount them as read/write? Or mount symlinks etc, like magisk did?
Sorry for asking stupid question, but I saw that the /system/etc/firmware from the zip is being copied to $SYSTEM/etc/firmware to the phone which was given variable as /system. Isn't that what you mean?
There are another errors:
Code:
cp: can't create '/system/etc/firmware/*': No space left on device
cp: can't create '/system_root/init.nethunter.rc': Read-only file system
grep: /system_root/init.rc: No such file or directory
sed: /system_root/init.rc: No such file or directory
chown: /tmp/nethunter/boot-patcher/ramdisk/*: No such file or directory
find: /tmp/nethunter/boot-patcher/ramdisk/*: No such file or directory
Thanks for the help!

in case there exist /system symlink, bind mount might fail. you could rename it by adding setup_mountpoint above this line (it probably would also work if set SYSTEM=/system_root/system, not quite sure what's intended for that variable)
Code:
setup_mountpoint /system;
$BB mount -o bind /system_root$system /system;
for rw access you need TWRP with dynamic partitions support. or re-create super.img with this script
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com

aIecxs said:
in case there exist /system symlink, bind mount might fail. you could rename it by adding setup_mountpoint above this line (it probably would also work if set SYSTEM=/system_root/system, not quite sure what's intended for that variable)
Code:
setup_mountpoint /system;
$BB mount -o bind /system_root$system /system;
for rw access you need TWRP with dynamic partitions support. or re-create super.img with this script
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
There are 3 update-binary files. Not sure which one to edit. and I checked all three but didn't find that exact line.
update-binary files
But i found these lines. Should i edit like this?:
Code:
if is_mounted /system_root; then
mount_apex;
if [ -f /system_root/build.prop ]; then
$BB mount -o bind /system_root /system;
else
setup_mountpoint /system;
$BB mount -o bind /system_root/system /system;
fi;
fi;
Thanks!

No clue what this warning means
Code:
[ 140.819754] (0)[460:recovery]Start 0x6000 of disk mmcblk0 not write group aligned
[ 140.819794] (0)[460:recovery]End 0x6000 of disk mmcblk0 not write group aligned
[ 140.820304] (0)[460:recovery]0x140000 ~ 0x144000 of mmcblk0 is partially write protected
might be related to that
Code:
[ 140.467184] (1)[278:teegris rpmb]TZDEV ERR tzdev_teec_connect(60): Failed to connect to root_task socket after 20 retries
[ 140.467211] (1)[278:teegris rpmb]TZDEV ERR TEEC_InitializeContext(208): Failed to connect to root task, context = 0000000000000000 ret = -111
my guess these are only QSEE related partitions somehow protected by kernel. you can check partition names by resolving the by-name symlinks.
Code:
ls -l $(find /dev/block -name by-name)/*

aIecxs said:
No clue what this warning means
Code:
[ 140.819754] (0)[460:recovery]Start 0x6000 of disk mmcblk0 not write group aligned
[ 140.819794] (0)[460:recovery]End 0x6000 of disk mmcblk0 not write group aligned
[ 140.820304] (0)[460:recovery]0x140000 ~ 0x144000 of mmcblk0 is partially write protected
might be related to that
Code:
[ 140.467184] (1)[278:teegris rpmb]TZDEV ERR tzdev_teec_connect(60): Failed to connect to root_task socket after 20 retries
[ 140.467211] (1)[278:teegris rpmb]TZDEV ERR TEEC_InitializeContext(208): Failed to connect to root task, context = 0000000000000000 ret = -111
my guess these are only QSEE related partitions somehow protected by kernel. you can check partition names by resolving the by-name symlinks.
Code:
ls -l $(find /dev/block -name by-name)/*
Click to expand...
Click to collapse
Thanks @aIecxs, i think these errors aren't in the way of flashing, because i flashed magisk successfully(working!) despite of the same errors. My main concern is getting the problem you stated fixed, that is, /system/etc/firmware isn't getting copied, /system_root being Read-only file system
Code:
cp: can't create directory '/system_root/sbin': Read-only file system
find: ak_patches/: No such file or directory
Please look at my latest recovery.log. It maybe different and provide hints.
Thanks!

Regardless how the flashing went, The kernel seems to be installed. Because I checked that the Stock kernel doesn't support either NFS Client or nfs-kernel-server, and HID interfaces. Another noticeable change was, before flashing my kernel, I could not set my SELinux to permissive(I did not modify this intentionally, I followed a documentation.)
After i installed the kernel, Both of them are working without problems. SELinux is now modifiable.
After each reboot, I get notification:
Android System
There's an internal problem with your device. Contact your manufacturer for details.

Database Info

welcome