Database Users

[Q] Mounting ext4 as data before boot + PA 2.00

Hi everyone.
I'm trying to increase data partition storage by using ph03n!x walkthru on Paranoid Android 1.992 and 2.0. I'm stuck at extracting boot.img in Working folder. The rom.zip itself don't have boot.img or boot folder so after extracting PA rom in dsixda kitchen i copied boot.img from Nandroid backup on SD. But while im trying to extract that boot.img there's an error
Code:
Working folder found
Android 'magic' header not found at start of boot.img
Cheching if it exists elsewhere ...
Warning: Android header not found in boot.img (unsupported format)
Error: kernel offset (page size) is 0
Press Enter to continue
So i took recovery.img from nandroid backup, renamed it to boot.img and extracting went fine, but there was some problems: could not find init.htcleo.rc file and "on fs" lines in init.rc file
Any suggestions how to do it? I think that real init.rc is placet in boot.img (not recovery.img), but how to extract it?

Do you have a working folder setup? If you do, then forget about the boot.img, just place the 'boot' directory from the ROM's zip (under /kernel/). If you do not have a Working folder setup, then follow my instructions to create a temporary ROM zip with the required folders - meta-inf, system and boot.

ph03n!x said:
just place the 'boot' directory from the ROM's zip (under /kernel/)
Click to expand...
Click to collapse
Thanks a lot ph03n!x. It worked And also thanks for this great mod (Initrd.gz was great, now its time for this new method )

clockworkmod

Hi guys, I had clockworkmod 5.0.2.6 installed but it was small(partition). I've found some clockwork mods with bigger partition(250, 400) in guide and downloaded them. I flashed them via daf and they've flashed successfully. Now, the problem is none of newer roms(ics, jb) work with that version of cwm. How to install other recovery(for eg. newer cwm)? Don't give me the guide, I'm sick of them and have a few bookmarked but there is no solution for that. Oh, I forgot. I have mag1.13 and cwm 3.0.0.8(orange one)..
Thanks in advance.

Shaumaaa said:
Hi guys, I had clockworkmod 5.0.2.6 installed but it was small(partition). I've found some clockwork mods with bigger partition(250, 400) in guide and downloaded them. I flashed them via daf and they've flashed successfully. Now, the problem is none of newer roms(ics, jb) work with that version of cwm. How to install other recovery(for eg. newer cwm)? Don't give me the guide, I'm sick of them and have a few bookmarked but there is no solution for that. Oh, I forgot. I have mag1.13 and cwm 3.0.0.8(orange one)..
Thanks in advance.
Click to expand...
Click to collapse
If your just looking to increase system partition then there is a file (flash.cfg I think) that you need to modify, open it and it should be fairly clear what to modify to increase the partition size.

I edited the flash.cfg with notepad++ and wanted to flash the same recovery again but daf is showing me some error.

first, in case you handt realised, increasing teh system size is only needed when the size required by your rom needs it, , , , so for example flashing a 200mb rom to a 400mb partition will waste 200mb, the system wont use that extra space. Your total available storage does NOT include teh system partition, sop teh bigger system partition you create, the lesws available internal storage you will have for data.
Look in the folder where flash.cfg is, , find recovery-raw.img and replace it with the new recovery .img you want to use.
Then, because of the line
recovery rrecov|ro|nospr filesize recovery-raw.img
in flash.cfg, when you run the flash it will create the correct recovery partition size.
(If the newer recovery didnt use a larger recovery partition, or if you wanted to reinstal recovery again after already doing the above, ((meaning the recovery partition is already big enough)) you would simply start cwm, and flash the new recovery from sd card, just like flashing a rom)
showing me some error.
Click to expand...
Click to collapse
completely useless sentence, you may as well not bother, how do we know what error it shows? mind reading?

This error
An error has occurred
Read below for more information
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: bad data size format
Info: .\RSPL\RSPL.cpp (428)

**** yeah! I did it!
Thanks bro'

I dindn't Heeeeeeeeelp..
I installed the cwm touch and when installing rom with aroma(pacman) it stays at 0% but it's putting files to system. Then it passes the mag and stays at bootanimation. Whats wrong?
EDIT: I'm uploading video of my problem

Fixed
Fixed with magldr repartitioning. Thanks anyway.

[Kernel] [Compilation] [Boot] SM-N910F

Hi,
I downloaded the SM-N910F kernel from samsung compiled and burned it with Heimdall. It works fine.
The problem I am facing is when I add some code into the kernel. It won't boot (returns do DOWNLOAD mode screen), error message "could not do normal boot".
Note: I have tried burning my boot.img both with Heimdall (linux) and Odin (windows), and get the same results, i.e. unmodfied kernel works fine, modified -- fails.
It seems to be a zImage size issue.
I tested this by only adding lots of seq_print(m ,"something somthing ....") in print_binder_transaction() (drivers/stagin/android/binder.c). just to make the zImage bigger (unmodified zImage size: 9792000 bytes, bloated zImage 9799072 bytes, only ~7Kb more).
I checked the with busybox fdisk the BOOT partition size, its 17MB.
I pulled the boot.img with dd from the device and used "abootimg -u boot.img -k ../arch/arm/boot/zImage" to update it with my compiled zImage.
any ideas?
missing info?
Thanks,
Daniel.

lightydo said:
Hi,
I downloaded the SM-N910F kernel from samsung compiled and burned it with Heimdall. It works fine.
The problem I am facing is when I add some code into the kernel. It won't boot (returns do DOWNLOAD mode screen), error message "could not do normal boot".
Note: I have tried burning my boot.img both with Heimdall (linux) and Odin (windows), and get the same results, i.e. unmodfied kernel works fine, modified -- fails.
It seems to be a zImage size issue.
I tested this by only adding lots of seq_print(m ,"something somthing ....") in print_binder_transaction() (drivers/stagin/android/binder.c). just to make the zImage bigger (unmodified zImage size: 9792000 bytes, bloated zImage 9799072 bytes, only ~7Kb more).
I checked the with busybox fdisk the BOOT partition size, its 17MB.
I pulled the boot.img with dd from the device and used "abootimg -u boot.img -k ../arch/arm/boot/zImage" to update it with my compiled zImage.
any ideas?
missing info?
Thanks,
Daniel.
Click to expand...
Click to collapse
ok, solved the problem. used unpackbootimg & mkbootimg to create the new boot.img. works fine...

Issue with flashing magisk on BlurOS (Asus t00j/t00f)

Hi Folks,
I am new to rooting and struggling with a problem. I have an old zenfone 5(ASUS_T00J) model. I am using custom rom BlurOS found in the below thread:
https://forum.xda-developers.com/zenfone-5/development/rom-bluros-version-1-0-zenfone-5-t3619058
I am trying to flash Magisk from TWRP recovery but it's failing with below error:
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Invalid Block device on '/dev/block/zram0
none
swap
defaults
zramsize=67108864
', 'swap', 36
Updating partition details..
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/Download/Magisk-v20.4(20400).zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
**********************
Magisk 20.4 Installer
**********************
- Mounting /system
- Target Image: /dev/block/by-name/boot
- Device platform: x86
- Constructing environment
- Adding addon.d survival script
E: Error executing updater binary in zip '/sdcard/download/Magisk-v20.4(20400).zip'[/QUOTE]
Error flashing zip '/sdcard/download/Magisk-v20.4(20400).zip'
Updating partition details...
...done
Updatrer Scripts are in below Google Drive Location:
https://drive.google.com/file/d/1SdtXdgB-iCB1X5PL3OCsZLrcUT6WlRzX/view?usp=sharing (Updater Script)
https://drive.google.com/file/d/1X2lupRfMUj-n5pRx2c0h0NQHUvfOXJAP/view?usp=sharing (Updater Binary)
Steps followed by me:
1. Installed latest Magisk manager from GitHub
2. Downloaded the latest zip file prompted by Manager
3. Reboot in TWRP recovery
4. Flashed the newly downloaded zip file
Appologies in advance if this is not the right forum or I have violated any guidelines. Let me know if you need any more details from my side. Thanks in advance.

Update
The issue still remains. Tried to find solutions online. Below methods were suggested. Since, I am new to this, might have tried something silly in the process.
Method 1:
Flash the Rom boot image via TWRP
Result: Did not prompt to provide any partition but Failed with error 'No Partition selected for flashing'. Updated the TWRP to 3.2.3 and tried the same thing again. This time prompted for a partition but no option was available that I could provide there and failed with the same error.
Method 2:
Patching the Boot image of my ROM through magisk patch
Result: Extracted the boot image for BlurOS Custom rom and tried to patch it through magisk Manager. Installation failed with 'Unable to repack boot image'.
Since I updated the TWRP, tried to flash the magisk zip file hoping for some other error (at least). It failed with below error message:
Installing zip file '/sdcard/Download/Magisk-v20.4.zip'
Checking for digest file...
Skipping Digest check: No digest file found
*************************
Magisk 20.4 Installer
*************************
- Mounting /system
! Unable to detect target image
- Unmounting partitions
Updater process ends with error: 1
Error Installing zip file
Updating partition details...
... done
Kindly let me know if you guys have any pointers. Any leads will be appreciated.

Magisk is unable to patch x86 boot.img's, so you have to use "android image kitchen"
Magisk patches Ramdisk file so you have to do:
move x86 ramdisk to ARM boot.img
Patch it via magisk
move patched ramdisk back to x86 boot.img
You can try boot.img's that I made for RR and Lineage in my thread. They are pre-patched with magisk 20.4
Anyways, is BlurOS better than lineage or RR ?

Lineage Install fails with Error E1001: Failed to update system image, ERROR 7

Hi,
I am trying to install the latest Lineage version on my Samsung Nexus 10 via twrp, but so far it always immediately fails with
Error E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-17.1-20220318-UNOFFICIAL-manta.zip'
I tried wiping the entire system, cache and all and I tried both the adb push method and sideloading adb and they all produce the exact same error.
This is my first time doing this type of thing, so any help would be greatly appreciated.
P.S. I am currently running Windows 10, but could boot into a Linux Live Medium if that would be useful.
Edit: I was following this tutorial for the setup.

I'm facing exactly the same issue here with the installation of `lineage-17.1-20220919-UNOFFICIAL-manta.zip` file.
I'm currently on the latest original Google Android ROM flashed with `image-mantaray-lmy49j.zip` and want to update the system to the lineage OS as above.
I'm using TWRP v3.6.2_9.
What I did:
- uploaded `lineage-17.1-20220919-UNOFFICIAL-manta.zip` to `/sdcard` location;
- wiped out `dalvik-cache` and `cache` partitions;
- tried to install `lineage-17.1-20220919-UNOFFICIAL-manta.zip` as a single installation file;
Got this error. Here is an output from recovery.log:
Code:
Installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Unmounting System...
I:Update binary zip
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
No path given to file labeling backend
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keysTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keys
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
Backup/restore is not possible. Partition is probably empty
Patching system image unconditionally...
performing update
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/4dd6bf24fbba9cc76c352f5c4cfaed0074be0244
535756800 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 3367 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,225950,228864,229947,230400]
new data receiver is still available after executing all commands.
Patching system image unconditionally...script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Does anyone have any clue on what could be wrong here and why it fails?

unpack zip remove lines, then pack zip and try again. voilla
or utube eroor 7

I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!

Cpluo said:
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Click to expand...
Click to collapse
Not enough space on /system. Resize the partition. After 17.1 is running for me. https://www.hovatek.com/forum/thread-32750.html

Thanks a lot Daniel! I will try your way.