Database Users

[Q] [Help] Problem with NAND Kitchen

Hello
I would like to use Android on my HD2. I was searching and testing many ROMS but I didn´t find any rom which is usable for me. I would like to have a ROM that is without Sense, has Multilanguage support and is on Android 2.2 version.
So I decided that I would make my own.
0) I was reading
HTML:
http://forum.xda-developers.com/showpost.php?p=10291851&postcount=1
and made this procedure.
1)downloaded some ROM from here
2)unpacked this rom in linux with :
Code:
unyaffs system.img
then I got this directories:
Code:
app bin build.prop etc fonts framework lib media usr xbin
3)I downloaded update-cm-6.1.1-N1-signed.zip from CyanogenMod Forum > Downloads > Stable Mod > Nexus One and unpacked. I got : META-INF system boot.img.
4)I copied everything what was described step 0 from directories from step 2 to directory system from step 3
5)I downloaded and copied build.prop from step 0 to system
6) I updated permition like it is described in step 0
7) I created system.img with command : mkyaffs2image . ../system.img
Then I copied this system.img from linux to my windows and put this file in directory in which was different NAND rom. (replaced system.img). After that I flashed my phone and it did not work. Screen was frozen after booting and only green HTC was on display.
Can somebody please help me and give me some advice or some small howto. Does anybody know what can be wrong?
UPDATE: If I unpacking any nand roms and packing back everything is ok They must by any problem in me procedure of creating.
Thank you
Michal Fichtner

kitchen rom

I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?

stefano_te said:
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
Click to expand...
Click to collapse
I think it's enough that you throw it into the SystemUI.apk(have a look inside that apk, if it's not there then it is in secframework.apk) (/res/.../XHDPI). Open the apk in winrar (you might have to rename it from .apk to .zip) and drag and drop the new files. Decompiling isn't necessary for this sort of thing.
Also, check this out:
http://forum.xda-developers.com/showthread.php?t=1918500
I did this a long time ago so some of what I just said might be wrong, if you need more help then just say so.

I would like to use as a basis the stock rom 4.1.2 : N7000XXLT9_N7000ITVLT3_ITV.zip
I used the kitchen to create workfolder following all the steps suggested by the program , I found the following problems:
1 ) during the procedure appeared to me the following warning :
Warning : A valid boot.img is not found . You have the option to add a
' fake ' boot.img So THAT the features of the kitchen can still
function normally.
This boot.img will be automatically removed from your ROM 's
ZIP file When Is It built .
Add boot.img (y / n)? (default: y) "
is this normal? how to solve ?
2 ) Working folder information ( v)
Android OS version: 4.1.2
Device: GT- N7000
Model: GT- N7000
ROM Name : JZO54K.N7000XXLT9
CSC version: It 's normal that there is nothing written here ?
Rooted ( Superuser app + su) : NO
Rooted ( unsecured boot.img ) : UNKNOWN how I fix this ?
BusyBox installed : NO
BusyBox run-parts support: UNKNOWN UNKNOWN how I fix this ?
Apps2SD (Apps to EXT) enabled: NO
/ data / app enabled: NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support: NO
/ system / framework is deodexed : NO
/ system / app is deodexed : NO
modem.bin found: YES
ROM will wipe all data : NO
3) throughout the META-INF folder there are only 2 files: update-script; update-script.bak
4) scripts / get_api_level: line 18: more: command not found
5) I checked the update-script and there are 3 warning in the report:
7/101: copy_dir PACKAGEystem SYSTEM:
8/101: format PRELOAD:
>> WARNING: Partition not recognized
9/101: copy_dir PACKAGEreload PRELOAD:
>> WARNING: PRELOAD: not found in working folder
10/101: symlink dumpstate SYSTEM:bin/dumpcrash
11/101: symlink toolbox SYSTEM:bin/cat
82/101: set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
83/101: run_program PACKAGE:create_preload_symlinks
>> WARNING: create_preload_symlinks not found in working folder
84/101: set_perm 0 3003 06755 SYSTEM:bin/ip
How do I resolve this? I tried a lot of on-line but have not found anything. My goal is to make me a custom rom from the last stock (LT9) ... what should I do?

Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.

ThaiDai said:
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
Click to expand...
Click to collapse
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?

stefano_te said:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
Click to expand...
Click to collapse
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.

ThaiDai said:
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
Click to expand...
Click to collapse
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)

stefano_te said:
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
Click to expand...
Click to collapse
No. Because you do this partly when using the kitchen step by step. Or when changing your updater-script.
The kitchen is a great help and simplifies cooking a rom - but it still is a little bit more complicated than heating baby food in the microwave. And if you really want your "custom" rom you should start to learn what happens in each step. And this can't be done by revealing everything...

how to repack system folder to system.img

Hi pls help me someone
my device :lenovo A3300-GV with 4.4.2 android version
i unpacked system.img file with ext4unpacker.exe and i add my favorite language to all apk on system/apps folder
now again how to repack system folders to system.img
i use this topic always but for system.img files from a3300gv 4.4.2 terminal show this below error :
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Click to expand...
Click to collapse

[CLOSED]Deleted.

Deleted by woltrex

Deleted by Woltrex.

Deleted by Woltrex

What would I need to change in our windows installer to help create the data.img the way you are? https://github.com/BlissRoms-x86/An.../Android_UEFIInstaller/BasicInstaller.cs#L210
proof I am no windows developer, I fudge my way through it

Hi Woltrex,
Could you please adapt your toolbox to work with Android-x86 8.1-rc1? If I try to edit data or system images with your current toolbox the system doesn't boot.

the tools link is nothing but advertisements. Can't make this work

ariadnejro said:
Hi Woltrex,
Could you please adapt your toolbox to work with Android-x86 8.1-rc1? If I try to edit data or system images with your current toolbox the system doesn't boot.
Click to expand...
Click to collapse
I will make the necessary arrangements in next version. :good:

DigitalMD said:
the tools link is nothing but advertisements. Can't make this work
Click to expand...
Click to collapse
I do not fully understand. What you mean?

electrikjesus said:
What would I need to change in our windows installer to help create the data.img the way you are? https://github.com/BlissRoms-x86/An.../Android_UEFIInstaller/BasicInstaller.cs#L210
proof I am no windows developer, I fudge my way through it
Click to expand...
Click to collapse
I need to check it. Is there a problem creating Data.img?

WoltreX said:
I need to check it. Is there a problem creating Data.img?
Click to expand...
Click to collapse
I think he means that when the Windows UEFI installer(that is linked in the Blissx86 OP) is extracting the contents of the iso onto the HDD partition that is selected.
He wants the installer to create the data.img in a similar manner as your tool does

WoltreX said:
I need to check it. Is there a problem creating Data.img?
Click to expand...
Click to collapse
arifqur said:
I think he means that when the Windows UEFI installer(that is linked in the Blissx86 OP) is extracting the contents of the iso onto the HDD partition that is selected.
He wants the installer to create the data.img in a similar manner as your tool does
Click to expand...
Click to collapse
^^ Yuppers ^^

Works great.. thank you woltrex

Bliss OS/Android PC Toolbox updated.
Changelogs v1.1
-Added Android-x86 Oreo support. You can unpack/repack android x86 images.
-Added fsconfig options. Android x86 images requires it. (I will add guide in first page about it)
-Increased stability and fixed some bugs.

I know what I say would be foolish but...
Remix OS Toolbox? (Lollipop&Marshmallow)

im having problem extracting bliss os system.sfs
Parallel unsquashfs: Using 4 processors
7362 inodes (20785 blocks) to write
write_xattr: could not write xattr security.selinux for file C:\Users\farivar\Downloads\APT\unpack\system/app/AmberTheme/AmberTheme.apk because you're not superuser!
write_xattr: to avoid this error message, either specify -user-xattrs, -no-xattrs, or run as superuser!
Further error messages of this type are suppressed!
[=================================-] 20785/20785 100%
created 6654 files
created 956 directories
created 708 symlinks
created 0 devices
created 0 fifos
Click to expand...
Click to collapse

farivar said:
im having problem extracting bliss os system.sfs
Click to expand...
Click to collapse
What is the problem? I am seeing system.sfs extracted %100.

Hi,
I'm having trouble getting a BlissOS system.img to work. I already have a working installation of BlissOS, but am trying to add Surface drivers. So I extracted the system folder and then packed system.img, but on booting the modified system, it's freezing just when it says it is starting android (before the boot animation appears).
Specific steps I used:
-unpack system.sfs
-added my drivers, modified fs_config.txt to include permissions for my drivers e.g., system/lib/firmware/config.bin 0 0 644
-repack system.img
-remove system.sfs and replace with system.img
I even tried to just unpack and repack system.img without the drivers and that didn't work for me either. Any suggestions for what I may be doing incorrectly?

DoughMucker said:
Hi,
I'm having trouble getting a BlissOS system.img to work. I already have a working installation of BlissOS, but am trying to add Surface drivers. So I extracted the system folder and then packed system.img, but on booting the modified system, it's freezing just when it says it is starting android (before the boot animation appears).
Specific steps I used:
-unpack system.sfs
-added my drivers, modified fs_config.txt to include permissions for my drivers e.g., system/lib/firmware/config.bin 0 0 644
-repack system.img
-remove system.sfs and replace with system.img
I even tried to just unpack and repack system.img without the drivers and that didn't work for me either. Any suggestions for what I may be doing incorrectly?
Click to expand...
Click to collapse
If you edit fs_config, you must repack with Android-x86 option. That drivers can be uncompatible with your system. So system can not boot. I did not encounter any problems with the edits I made. You should be careful when editing the .img files.

Deleted by woltrex

WoltreX said:
Deleted by Woltrex.
Click to expand...
Click to collapse
? what happened ?

[GUIDE]How to extract /system from Samsung S7 OTA/FW in Windows without a Phone

This is a complete working guide on how to extract the /system partition from a Samsung S7 FW/OTA package using Windows (This is the same package one might flash to their phone with ODIN.) You can get this FW/OTA package from sites like Samsung-Firmware.org & SamMobile.com. It is very likely this works (or parts of it duct-taped together ) on other Phone models,etc, but I vouch that this guide works on the Samsung S7. Please chime in if it works on other models & brands!
Intro:
I found a LOT of guides similar to this, but couldn't get any to work with the Samsung S7 packages! And there are MANY different versions of the tools I mention below, many not working! So be sure to use the tool versions I post below. Over much time, it was a tiny step with each new attempt until I finally got it...& wanted to share!
Purpose:
Why would anyone want to do this? If you're reading this thread and don't know the answer to that, then I'm confused But I'll answer anyway - What is the purpose of this thread?
You would want to do this because you're a ROM Developer and don't want to have to go through the time & trouble of installing an OTA, then do a dd/cat to get the system image, etc. (With this method you don't even need a phone, just a PC!)
You are using a custom ROM, but want a stock app; for example the custom ROM you're using has the Google Dialer/Phone app builtin, but you prefer the stock Samsung Phone. Doing the steps outlined here will yield a "system" folder in Windows that you can simply navigate to /system/app or /system/priv-app and copy over the apk to your phone and install it! (via ADB or phone File manager app, etc). Obviously not all apks will work. Or maybe you want the libraries from another phone OTA package in order for an apk to work, and so on...
You are just curious what's in the /system partition for an OTA package!
Tools:
7-Zip
LZ4
simg2img: "Clone or download"->Download ZIP
Ext2Explore (Same as Ext2Read)
Guide:
Download FW/OTA (TMB-G930TUVU4CRI2.zip) from SamMobile website (or whereever)
Use 7zip to extract TMB-G930TUVU4CRI2.zip to a folder
Use 7zip to extract AP_G930TUVU4CRI2*.tar.md5 to a folder (ignore "There is no correct record at end of archive" error)
Use lz4 to extract system.img.ext4.lz4 -> system.img.ext4
lz4 system.img.ext4.lz4​
Extract simg2img_win-master.zip -> \simg2img_win-master\
Copy system.img.ext4 to \simg2img_win-master\ folder
Rename system.img.ext4 -> system.img
Use simg2img_win-master to convert system.img -> system.ext4.img
Double-click convert.bat (or run in cmd prmpt) (This will take a few minutes)​
Create new folder to save contents in, eg: "C:\System"
Use ext2explore to mount system.ext4.img: Open ext2explore->File->Open Image->Select system.ext4.img
Click Save icon->Save to your new folder, eg: "C:\System"
Wait for it to extract. Once complete, enjoy!
Links & Useful Resources:
Tmobile Versions: https://support.t-mobile.com/docs/DOC-30276
Search Keywords:
(This section is here so this thread comes up in searches for the many errors I came across while trying to get this to work in both Windows & Linux. That's right! I tried in both OSs and actually got it to work first in Windows... & yet to get it to work in Linux!)
- losetup /dev/loop2 /media/sf_Share/system.img.ext4 ->warning file does not fit into 512-byte sector; the end of the file will be ignored
- mount /dev/loop2 /mnt/mysystem2 -> mount: /mnt/mysystem2: cant read superblock on /dev/loop2
- mount -t ext4 /media/system.img /mnt/mysystem6 -> wrong fs type, bad option, bad superblock on /dev/loop6, missing codepage or helper program, or other error
fsck /media/system.img -> ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open ...
The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate suberblock: ...

Reserved

Just happened to see this thread.
Dropping in the let you know for linux just do this
Code:
simg2img system.img.ext4 system.img
mkdir system
sudo mount -t ext4 system.img system/
Of course all work is done in the current working directory.
You can just copy whatever you want from this mounted loop device of the system.img or whatever.
This is what i do because it seems to be the fastest in terms of work.
Hope it helps. I prefer all android work on linux

kevin71246 said:
Reserved
Click to expand...
Click to collapse
oh man you saved my day thanks man none of the old method worked but this did wonders