Hello guys!
I have Lenovo Tab 3 [TB3-850M], unfortuantely I am trying to deodex the ROM but both methods in SuperR Kitchen failed.
1st Method using oat2dex: It fails and not fully deodex the ROM and gives a list of failed files [look at pictures]
2nd Method using baksmali/smali: It says it "succeeded" but it doesn't as when flashing the ROM it is unbootable as I got (While deodexing) Java Exception error that it couldn't find classes.dex in all the ROM files!
Please I tried all Marshmallow deodexers available on XDA but nothing seems to work, the most about-successful attempt was with SuperR oat2dex and Fulmics Deodexer but I got com.android.phone has stopped working message error loop and other apps such as Maps and Keyboard.
Thanks in advance!
P.S: If you want the system.img.ext4 and boot.img I will upload them on request as my internet is not that fast and you most probably need one from me because the one online doesn't seem to extract [I made mine by flashing the unextractable system.img using SP Flash Tool and make System Image Backup using TWRP and copied it to my PC]
Regards!
Troubleshooting
What Kitchen version?
1.1.5.9
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
Bash on Windows x64
What device are you working on (make/model)?
Lenovo Tab 3 LTE TB3-850M arm64
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
system.img.ext4 from TWRP Backup
What Android version?
Marshmallow 6.0
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
set_metadata
What did you do after extracting and before building?
Didn't mess with the files before and after building/extracting, just used the commands on SuperR and flashed the finished zip file to the tablet.
Were there errors on the screen if you scroll up in the terminal?
Mentioned the errors on the first post
Send a recovery.log after flashing if you have problems flashing the ROM.
No need because TWRP flash successfully
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
http://www.mediafire.com/file/r2p6hos5k73f161/TB3-850M-System.7z
Use the support option in the Misc Tools menu and attach the support.zip to your post.
I am not sure but looks like SuperR isn't making the support.zip, I will upload the project files instead (I think both are the same)
addas4 said:
What Kitchen version?
1.1.5.9
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
Bash on Windows x64
What device are you working on (make/model)?
Lenovo Tab 3 LTE TB3-850M arm64
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
system.img.ext4 from TWRP Backup
What Android version?
Marshmallow 6.0
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
set_metadata
What did you do after extracting and before building?
Didn't mess with the files before and after building/extracting, just used the commands on SuperR and flashed the finished zip file to the tablet.
Were there errors on the screen if you scroll up in the terminal?
Mentioned the errors on the first post
Send a recovery.log after flashing if you have problems flashing the ROM.
No need because TWRP flash successfully
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
http://www.mediafire.com/file/r2p6hos5k73f161/TB3-850M-System.7z
Use the support option in the Misc Tools menu and attach the support.zip to your post.
I am not sure but looks like SuperR isn't making the support.zip, I will upload the project files instead (I think both are the same)
Click to expand...
Click to collapse
I can't do anything about this. You would need to create an issue on the smali/baksmali github repo. Once it is fixed there, I can compile new jar files and update them in the kitchen. Check your deodex log for the smali/baksmali errors you will need to post when you create the issue/s
Related
Good evening,
I've written a module for my smartphone and I need to compose a rom to install on my device...
I followed some tutorials, so now I know how to build an android kernel, obtaining a zImage.
Now, a friend told me that I must make a backup with clockworkmod (done!) and download on my pc, than I can recover the boot.img from there and split them in ramdisk and kernel.
Now I can compile my new kernel and merge it (the obtained zImage?) with the ramdisk to have a new rom to flash on my device... is true?
But I don't know how I can split the boot.img (maybe with dsixda kitchen?) and how to create the new rom. I tryied som weeks ago with a .zip rom and the dsixda kitchen and I split and recomposed a rom, but files contained in the .zip files was different from files that I downloaded by my device...
Someone can explain me the correct way to do this process? Thank you!
Paolo.dev said:
Good evening,
I've written a module for my smartphone and I need to compose a rom to install on my device...
I followed some tutorials, so now I know how to build an android kernel, obtaining a zImage.
Now, a friend told me that I must make a backup with clockworkmod (done!) and download on my pc, than I can recover the boot.img from there and split them in ramdisk and kernel.
Now I can compile my new kernel and merge it (the obtained zImage?) with the ramdisk to have a new rom to flash on my device... is true?
But I don't know how I can split the boot.img (maybe with dsixda kitchen?) and how to create the new rom. I tryied som weeks ago with a .zip rom and the dsixda kitchen and I split and recomposed a rom, but files contained in the .zip files was different from files that I downloaded by my device...
Someone can explain me the correct way to do this process? Thank you!
Click to expand...
Click to collapse
So many u can use
1. http://forum.xda-developers.com/showthread.php?t=1619473
2. http://forum.xda-developers.com/showthread.php?t=2036528
3. http://forum.xda-developers.com/showthread.php?t=1877807
and many more if u search
Description: Utility (hereinafter - the kitchen) to make changes to the firmware image for the Lenovo K900.
Operating System Requirements: Any Linux-like system (I recommend Ubuntu), any digit. For correct working kitchen must be installed packges: p7zip, p7zip-full, jdk, jre, python, ia32-libs.
Features: Removing the preinstalled Chinese software from the VibeROM firmwares; other firmware - manual; deodexing firmware; adding ROOT rights in firmware; editing build.prop; installing Google apps (* not verified), repacking the system.img.gz image.
Instructions for use:
- unpack the archive to any folder;
- Run the kitchen with console command ./kitchen.sh and enter the root password (required for file operations);
- Copy the file system.img or system.img.gz in a folder /in/;
- Enter 1 if throwing system.img.gz image archive folder in /in/, or go to step 2 if the folder /in/ drop files system.img;
- Type 2 to mount the image, while in the kitchen wearing the phrase "System: unmounted" will change to "System: mounted". The system is mounted in a folder /mount/;
Then simply describe the menu items:
3 - removes Chinese preinstalled software according file cn-apps in /scripts/ folder;
4 - "easier" firmware by deleting unnecessary files, animation off; applies mods - Record video to MP4, boot animation changed to "clipped " (you can change your folder /scripts/mod/);
5 - deodexing firmware (it takes quite a long time , up to 10 min);
6 - adding ROOT rights (used SuperSU 1.93). If you want to use a different version, you can replace the files in the /scripts/root/;
7 - editing build.prop file by using gedit;
8 - Set the Google apps light with a minimum set of software, you can further install more right already from Google Market (not tested);
9 - edited image packaging system system.img.gz. Ready to pick up the file from the folder /out/;
10 - unmount mounted image. Performed at the end of all operations with an editable manner;
0 - unpack inb firmware;
x - exit.
Download link:
http://forum.xda-developers.com/devdb/project/dl/?id=5359
Download mirror:
https://drive.google.com/folderview?id=0Bz3X7ZuowQimM3c0ZFV2QlZMR2c&usp=sharing
XDA:DevDB Information
Lenovo K900 kitchen, Tool/Utility for the Lenovo K900
Contributors
xxx-man-by
Version Information
Status: Testing
Stable Release Date: 2014-02-17
Created 2014-02-19
Last Updated 2014-06-07
What a great job！:good:
Amazing
Now its time to cook some ROM's
Lenovo K900 kitchen 1.21 beta
Released new version 1.21 beta
Whats new:
- Added support for firmware format INB (unpacking only);
- SuperSU binaries updated to version 1.93;
- Added support for complex tools with Android 4.3 (deodex, zipalign, optipng). Work is not very stable.
great, I hv prepared ubuntu and hv started cooking
Released new version 1.23
Whats new:
- Changed the script for implementation Root rights firmware (to fully support Android 4.3)
Just asking...
no kitchen for Windows7?
pjsplayez said:
Just asking...
no kitchen for Windows7?
Click to expand...
Click to collapse
No. Only for Linux-like OS, because Windows cannot work with images, mounting, rights etc...
Thank you i try it and install root Good Job
Just ask
xxx-man-by.. why not just "inb" file in "sdfuse" folder ?!. thanks before
Thank you, I am being to buy that device ^_^
Dual boot
Hello, anyone know how the best way to dual boot os in my laptop?
i want to boot windows 7 with ubuntu.
Hope anyone can give me guide or give me any link to make a dual boot.
help XXX-Man
i think the link is not working anymore.
REupload please
pjsplayez said:
help XXX-Man
i think the link is not working anymore.
REupload please
Click to expand...
Click to collapse
Ok. I`ll upload to the mirror. Please wait. DONE.
pjsplayez said:
Hello, anyone know how the best way to dual boot os in my laptop?
i want to boot windows 7 with ubuntu.
Hope anyone can give me guide or give me any link to make a dual boot.
Click to expand...
Click to collapse
if you need linux just for cooking, dont install it to harddrive.. just throwit on some usb drive and run it live..
use pendrivelinux or yumi to make live linux on usb.
xxx-man-by, if we have already the unpacked system folder like the VIBEROM Dev1418?
sev7en said:
xxx-man-by, if we have already the unpacked system folder like the VIBEROM Dev1418?
Click to expand...
Click to collapse
I do not understand what you mean.
xxx-man-by said:
I do not understand what you mean.
Click to expand...
Click to collapse
Good morning,
to start my kitchen, I download the original VIBEROM image file, redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip but if I extract it on the "IN" folder I haven't the .img packages to mount (e.g. the system folder is already unpacked):
Also, after that, I get only the system.img file but in other release I used before, e.g. the one for the VIVO, I had the way to pack directly the image to flash. Here which one is the next step?
Thank you,
sev7en said:
Good morning,
to start my kitchen, I download the original VIBEROM image file, redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip but if I extract it on the "IN" folder I haven't the .img packages to mount (e.g. the system folder is already unpacked):
Also, after that, I get only the system.img file but in other release I used before, e.g. the one for the VIVO, I had the way to pack directly the image to flash. Here which one is the next step?
Thank you,
Click to expand...
Click to collapse
redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip - this is ordinary zip file, K900 kitchen is not working with OTA zip archives. To start working with kitchen you need to put in the /in/ folder only system.img, system.img.gz, or any INB file (to unpack it). Only like this.
xxx-man-by said:
redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip - this is ordinary zip file, K900 kitchen is not working with OTA zip archives. To start working with kitchen you need to put in the /in/ folder only system.img, system.img.gz, or any INB file (to unpack it). Only like this.
Click to expand...
Click to collapse
thank you for getting me back sooner, with your unique Kitchen we are able to manage that files as well to repack them but when done how we get the final package to flash?
thanks once again for that
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
th3magpi3 said:
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
Click to expand...
Click to collapse
see Introduction : How to build an Android ROM - XDA-University
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS] by lokeshsaini94
This thread will be moved to Android Q&A, Help & Troubleshooting
Some Basic things u need to Know before Porting
The rom which you want to port for your device is named here as PORT
The rom which is already working for your device is called here as BASE
First unpack system.new.dat in both port and base rom
For Ubuntu
Now we need to decompress .dat to ext4 img
Open terminal and
Now enter this command
./sdat2img.py system.transfer.list system.new.dat system.img
By running this command u can see a system.img
decompress ext4 img to output folder
Now we will mount system.img
Enter this command
sudo mount -t ext4 -o loop system.img output/
Now go to output folder and now u can see all folder and apk like a KitKat rom
Now do the same with port rom
Click to expand...
Click to collapse
For windows use System Extractor for unpacking
1. Delete app,font,framework,media and priv-apps in base rom
2. Copy app,font, framework,media and priv-apps from port to base
3. Copy handheld_core_hardware.xml and platform.xml in system/etc/permissions from port to base
4. Copy 00banner in system/etc/init.d from port to base
5. Now open build.prop in both base and port for editing rom version and other things.It is different in different roms. For CM edit
ro.cm.version=
ro.cm.releasetype=
ro.modversion=
ro.cmlegal.url=
ro.cm.display.version=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.config.ringtone=
Note: You have copy the above lines from port to base. Don't forget to add your device name in place of port rom's device name
6. Copy these files in system/lib from port to base I repeat from port to base
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
For AOSP based ROMs other library files are also needed for boot up. For example Dirty Unicorn needs
libgui.so
libsurfaceflinger.so
libsurfaceflinger_ddmconnection.so
libwifi-service.so
If you are porting a 64 bit ROM copy these files in system/lib64 too from port to base
7. Unpack boot.img of both base and port rom and open init.environ.rc in ramdisk. Copy and replace all the lines starting from "bootclasspath" from port rom's environ.rc to base rom's environ.rc and repack boot.img . Use Android Image Kitchen for unpacking and repacking boot.img
8.Now we need to compress the base rom
For Ubuntu
Now enter this command
./make_ext4fs -T 0 -S file_contexts -l 1073741824 -a system system_new.img output/
Now u can see ur system_new.img
now we need to compress it back to .dat
Now enter command
./rimg2sdat my_new_system.img
Now u can see system.new.dat
Click to expand...
Click to collapse
For Windows, System Extractor has an option to repack but it causes bootloop for me. Ignore step 8 if it causes bootloop
NOTE: You'll need a different updater script for unpacked system
9. Zip it back and Flash
Downloads
sdat2img.py
make_ext4fs
rimg2sdat
Now Download all these tools and paste it to ur base and port rom directory then follow instructions to port lollipop roms
Click to expand...
Click to collapse
CREDITS
VigneshS007
xpirt
matrixex
How to fix bootloop
Some Roms may not boot even after doing everything correctly. This method should be only used when nothing works
1. Copy all the files in system/lib, and system/lib64 if it's a 64 bit ROM, from port to base except the these files and folders
drm
hw
modules
soundfx
libGLES_trace.so
libGLESv1_CM.so
libGLESv2.so
libGLESv3.so
I repeat you have to leave the above files and folders and copy all the other files in system/lib from port to base.
If it still doesn't boot follow the second method
2. Unpack boot.img of both base and port, enter ramdisk and copy these files from port rom's ramdisk to base rom's ramdisk
seapp_contexts
sepolicy
service_contexts
Repack boot.img and flash it
IMPORTANT: This method should only be used when nothing works and if it boots after copying all the lib files, you will have to figure out which lib files are causing bootloop because port rom libraries will create many bugs.
Reserved
From who smartphones we can ported roms ?
Sparco21 said:
From who smartphones we can ported roms ?
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/List_of_Qualcomm_Snapdragon_devices
6.2 Snapdragon 410 and 412
Missing in this list:
Ark Benefit
Elephone Trunk
thanks for releasing the guide
Thanks for the tutorial!
Tried porting slim6 from redmi 2 but got stuck on bootanimation forever.What Im I supposed to do with the build.prop?
I already tried
-not touching it
-replacing it
-replacing some things
all ended in just bootanimation :/ I use the nexus 6.0 rom for base
BTW should I replace kernel(zimage) in boot.img(havent done it)?
Whenv i try to repack the system folder to system.new.dat with the Extractor for Windows i always get the following error: "It seems like the extractor not worked with your provided system folder please contact me for help".
I have read that specially the CM roms give this error but i cannoy understand how to fix it even after search the solution.
The rom i was trying to port is a CM12.1 rom. Anyone knows how to solve this?
mustang_ssc said:
Whenv i try to repack the system folder to system.new.dat with the Extractor for Windows i always get the following error: "It seems like the extractor not worked with your provided system folder please contact me for help".
I have read that specially the CM roms give this error but i cannoy understand how to fix it even after search the solution.
The rom i was trying to port is a CM12.1 rom. Anyone knows how to solve this?
Click to expand...
Click to collapse
Do you have python installed ?
mshoaib7 said:
Do you have python installed ?
Click to expand...
Click to collapse
Should i had to install Python in Windows? I didn't know Python exists in windows.
mustang_ssc said:
Should i had to install Python in Windows? I didn't know Python exists in windows.
Click to expand...
Click to collapse
Yes it does exist for windows. And if it still doesn't work ask this in system extractor thread
mshoaib7 said:
Yes it does exist for windows. And if it still doesn't work ask this in system extractor thread
Click to expand...
Click to collapse
I have just tried it but still the same issue.
I saw that the dev of the system extractor tried to explain how to solve the issue but honestly i don't undestand nothing of the process he's talking about, i was completely confused. For example, for some reason he was talking about the updater-script but i don't understand what relation are between what i want to do (repack the system folder) and the updater-script (located in the meta-inf folder).
Not booting, porting same vendor ROM but different model similar specs
Followed your tutorial till the last solution but no luck. I am trying to port my own device ROM but of a different model. I have Qiku Q Terra 808, model CP8692_I02 with 360 OS v21 and was trying to port v109 360 OS of model CP8692. The specs and everything is same however I am still unable to boot. There was a very weird thing happened when I flashed the ported ROM and restored the backed up data before booting. The device booted but it reboots on it's own in less than a min of booting and the cycle goes on. And if don't restore the data it goes in bootloop right away. I get the display on, optimizing apps then reboots and cycle goes on. The 360 OS are known for security and the device has fingerprint scanner. Do you think the stored fingerprint is causing issue in flashing new ROM or incorrect update script is the culprit?? Please advise.
@mshoaib7 Awesome tutorial man...??
CM14 theme engine has not been integrated at present, many functions is still in the invalid state, would you be interested in transplantation AOSP 7.1?
Very good ?A great help ?Moto g 2015
mshoaib7 said:
How to fix bootloop
Some Roms may not boot even after doing everything correctly. This method should be only used when nothing works
1. Copy all the files in system/lib, and system/lib64 if it's a 64 bit ROM, from port to base except the these files and folders
drm
hw
modules
soundfx
libGLES_trace.so
libGLESv1_CM.so
libGLESv2.so
libGLESv3.so
I repeat you have to leave the above files and folders and copy all the other files in system/lib from port to base.
If it still doesn't boot follow the second method
2. Unpack boot.img of both base and port, enter ramdisk and copy these files from port rom's ramdisk to base rom's ramdisk
seapp_contexts
sepolicy
service_contexts
Repack boot.img and flash it
IMPORTANT: This method should only be used when nothing works and if it boots after copying all the lib files, you will have to figure out which lib files are causing bootloop because port rom libraries will create many bugs.
Click to expand...
Click to collapse
shoaib bhai is this guide also for nougat roms?
MR.HACKER5476 said:
shoaib bhai is this guide also for nougat roms?
Click to expand...
Click to collapse
No, only some of the nougat Roms boot with this guide
Some one can port VIVO Y21L ROM & kernel for Lenovo A6000....
VIVO Y21L has same SD410 chipset as Lenovo A6000. @With support of VoLTE and OTG....
It not complete Guide
If you port tw roms,You will not get bootup.
Tried to port J5 rom or grand prime rom?
The tools that I've tried are for earlier versions of Android does anyone know of a working tool? My goal is to downgrade the kernel 1 versoin on my Note 5 AT&T with a locked bootloader.
N920AUCS3CPK1 but running the N920AUCS3CPJ1 kernel.
Update on useful tools:
Assayyed Kitchen for Windows https://forum.xda-developers.com/ch...-android-roms-editor-assayyedkitchen-t3410545
Assayyed takes the system.img you retrieve from decompressing your firmwares AP file. (typically 1 of 4 files known as combination files used to flash to Odin). This tool debloats, deodex, deknox and remove apps from system. In addition it allows you to unpack the kernel (boot.img) and recovery.img files! You can manipulate some settings in Assayyed (see the thread) or even directly as the image is extracted inside of your work folder for both kernel and recovery. You can replace init, change settings in english and etc. Then Assayyed allows you to repack the tool and I can confirm on sm-n920a nov 1 2016 firmware you can flash the repacked image, booting I need to test on a less expensive device first.
(I don't know if it correctly adjusts file permissions in Windows honestly I didn't boot with the final image I only tested that I could flash it, which I could with heimdall for Ubuntu directly from github using .pit file from current firmware csc file).. I have a thread
Carliv Image Kitchen
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
This tools is strictly for unpacking/repacking the boot.img and recovery.img files, may have other features I been focused on kernel/recovery. It has some really cool features which I am just learning but the great news is it's available in Ubuntu (also Windows I believe.)