Now I'm using rage kernel 3.0 (GB). The the problem is everytime I install newer version Bysybox and reboot my phone it will revert to version 1.19.3-cm71 with. So, My Backup, Lucky Patcher, etc. doesn't work properly. Since I can't find many GB kernel, can I remove/disable kernel's autoroot?
Thanks.
PS. My phone is Xperia Active (ST17i SATSUMA)
Rapier- said:
Now I'm using rage kernel 3.0 (GB). The the problem is everytime I install newer version Bysybox and reboot my phone it will revert to version 1.19.3-cm71 with. So, My Backup, Lucky Patcher, etc. doesn't work properly. Since I can't find many GB kernel, can I remove/disable kernel's autoroot?
Thanks.
PS. My phone is Xperia Active (ST17i SATSUMA)
Click to expand...
Click to collapse
Yes, you can remove the kernel's autoroot feature. You will have to unpack the ramdisk and remove a few lines in the init.rc file. These lines can be deleted -
Code:
#DooMLoRD: launching autoroot
start autoroot
# DooMLoRD: autoroot service
service autoroot /sbin/autoroot.sh
user root
oneshot
disabled
Then repack the ramdisk and boot.img file. Good luck
abcdjdj said:
Yes, you can remove the kernel's autoroot feature. You will have to unpack the ramdisk and remove a few lines in the init.rc file. These lines can be deleted -
Code:
#DooMLoRD: launching autoroot
start autoroot
# DooMLoRD: autoroot service
service autoroot /sbin/autoroot.sh
user root
oneshot
disabled
Then repack the ramdisk and boot.img file. Good luck
Click to expand...
Click to collapse
Ah, thanks. But it seem like I have to start to study about kernel.Can you give me some guide?
Rapier- said:
Ah, thanks. But it seem like I have to start to study about kernel.Can you give me some guide?
Click to expand...
Click to collapse
I would recommend you to use Android Kernel Kitchen as it is fully automated and does the job perfectly. All instructions are provided within the tool itself. You can find Kernel Kitchen here - http://forum.xda-developers.com/showthread.php?t=1659584
Or you can see this tutorial too - http://forum.xda-developers.com/showthread.php?t=2316750
abcdjdj said:
I would recommend you to use Android Kernel Kitchen as it is fully automated and does the job perfectly. All instructions are provided within the tool itself. You can find Kernel Kitchen here - http://forum.xda-developers.com/showthread.php?t=1659584
Or you can see this tutorial too - http://forum.xda-developers.com/showthread.php?t=2316750
Click to expand...
Click to collapse
can I change kernel logo with it?
abcdjdj said:
Yes, you can remove the kernel's autoroot feature. You will have to unpack the ramdisk and remove a few lines in the init.rc file. These lines can be deleted -
Code:
#DooMLoRD: launching autoroot
start autoroot
# DooMLoRD: autoroot service
service autoroot /sbin/autoroot.sh
user root
oneshot
disabled
Then repack the ramdisk and boot.img file. Good luck
Click to expand...
Click to collapse
I've manage to extract the boot.img. But I can't find init.rc file anywhere. Did I do something wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And in what program I can edit it?
Edit: Now I successfully extract the ramdisk using manual alternating method. Thanks.
prantoroy said:
can I change kernel logo with it?
Click to expand...
Click to collapse
Yes. The kernel logo is in the rle format. But Kernel Kitchen allows you to convert normal pictures to rle and vice-versa. So to change the kernel logo you must replace logo.rle
@abcdjdj, I just extracted the builded boot.img and I found that the command line is still there. I think the problem is here:
It asked for configuration file after I select build boot.img (with edited ramdisk of course). What should I do here? Select the "before edit ramdisk" one?
Rapier- said:
@abcdjdj, I just extracted the builded boot.img and I found that the command line is still there. I think the problem is here:
It asked for configuration file after I select build boot.img (with edited ramdisk of course). What should I do here? Select the "before edit ramdisk" one?
Click to expand...
Click to collapse
When you split the boot.img it must have asked to save the configuration so try building the boot.img with that configuration.
abcdjdj said:
When you split the boot.img it must have asked to save the configuration so try building the boot.img with that configuration.
Click to expand...
Click to collapse
I just tried it. And after create a new boot.img, I tried extract it again to see if it work. But it appear that init.rc still have the lines that I delete before.
Edit: Now, I'm done with it. I just forget to re-build the ramdisk so it use the old one. Now, I just flashed the new boot.img to my phone and it doesn't boot. It does vibrate one time but nothing more.
Note:
The command lines I delete is not exactly the same as you point it's
Code:
#DuMOHsmol:
instead of
Code:
#DooMLoRD:
And I do delete some blank lines. Is this the cause?
More SS:
Related
apk manager (backup, install, delete apks on phone )--- link: soon
custom boot image toolkit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
azuzu kitchen --- link: soon
nandroid2pc ( xrecovery backup copier / unpacker to pc) --- link: soon
aZuZu amend syntax update-script to edify syntax updater-script converter
RamDisk Packer for Windows
Small Library Dependency Scanner - Alpha
Direct SIN & YAFFS UnPacker
Old version of SIN2IMG UnPacker
how to use this?
you place init files in some folder for example ramdisk
then
aSmallPacker ramdisk.tar [folder name]
and you will get packed init files in ramdisk.tar with linux perms as normal user.
it is for users not having linux and wanna normal ramdisk.
Thanks mate, my linux drive got damaged, and I was searching a tool like this!, you really saved my ass
EDIT: Wrong file?, can't unzip
EDIT2: Forget it unzip with 7zip
EDIT3: Made a little .bat to make it easier download here
i've got this..please see my attach...is it i'm wrong?. i allready have ramdisk folder(include all thing from extracting ramdisk.tar) in the azuzu small packer folder..
sorry if i asking this cuz i'm noob
cruizz said:
i've got this..please see my attach...is it i'm wrong?. i allready have ramdisk folder in the azuzu small packer folder..
sorry if i asking this cuz i'm noob
Click to expand...
Click to collapse
Is not aSmallPacker [forder name] ramdisk.tar
it's aSmallPacker ramdisk.tar [forder name]
Also i made a .bat to make it easier for noobs, you can download post #4
i wanna ask bout how to add the ramdisk into system after we've moded and pack it?thanks before
cruizz said:
i wanna ask bout how to add the ramdisk into system after we've moded and pack it?thanks before
Click to expand...
Click to collapse
remount system rw and copy ramdisk.tar in /system/bin
thanks for the fast response mate ...what i mean is the set permission on it
cruizz said:
thanks for the fast response mate ...what i mean is the set permission on it
Click to expand...
Click to collapse
i use chmod 0755 w/o any problems
updated / fixed
nice mate . wondering if those tools repackage into one tool...your tools is very helpfull
RAMDisk Tool Final Added. Enjoy!
new version of custom boot image toolkit is up!
minor fixes ...
added image to android logo & android logo to image ( external tools ) ( cygwin again! god damn! )
working on new ramdisk handle procedure ... soon will be fixed
thanks DooMLoRD for finding tools
Can't unpack system.sin from WT19i_4.0.1.A.0.283_(1254-1854).ftf.
In cmd everything is ok, but after unpacking winrar can't read .img file.
.: SID :. said:
Can't unpack system.sin from WT19i_4.0.1.A.0.283_(1254-1854).ftf.
In cmd everything is ok, but after unpacking winrar can't read .img file.
Click to expand...
Click to collapse
did you use upgraded version from today or older one?
With Direct SIN & YAFFS UnPacker everything works fine! Grand merci!
hi...
how do u cpio.gz the ramdisk?
I get the 'afct is nt recognised as internel or external comand, operable program or batch file'
How do I .gz the ramdisk folder?
hi azuzu and thx but how to use custom boot image toolkit is ther any tuto ??
thx in advance
Not works the download links the firs post.....
apk manager (backup, install, delete apks on phone )--- link: soon
custom boot image toolkit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
azuzu kitchen --- link: soon
nandroid2pc ( xrecovery backup copier / unpacker to pc) --- link: soon
aZuZu amend syntax update-script to edify syntax updater-script converter
RamDisk Packer for Windows
Small Library Dependency Scanner - Alpha
Direct SIN & YAFFS UnPacker
http://azuzu.spice.net.au/tools/aKSTK/aKSTK.zip
very nice!!!
on project, your tool look good... i'm wating the result.. the first release...
thank to try to make our cooking easyer ...
This is very appreciated!
When will links be up?
Thanks for the tools
*solved* ...
a1exander said:
Can someone please tell me on how do open/edit .so files like gralloc or copybit?
Click to expand...
Click to collapse
.so files are linux libraries.... something like .dll in windows...
afaik (though i could be wrong) they cannot be edited... they need to be recompiled from sources to make any changes...
*solved* ...
a1exander said:
Can you please give me a quick little guide on how to do that?
Im kind of new to "developing".
Click to expand...
Click to collapse
i am also new to compiling stuff from sources so cant really help u there...
but if u want to look at CM7 sources u can always keep checking https://github.com/freexperia/FreeXperia
*solved* ...
a1exander said:
I see the gralloc there, but how do I compile it?
I really appreciating you people helping!
Click to expand...
Click to collapse
check out the make file:
https://github.com/freexperia/FreeXperia/blob/master/android-cm7/device/se/x10/libgralloc/Android.mk
Wow, that didnt take long. Please stay on topic guys.
Sent from my X10i using XDA Premium App
a1exander said:
Sry, but how do I get the libgralloc from FreeXperia github into gralloc.so file?
EDIT: Android NDK right?
Click to expand...
Click to collapse
If you're on Windows: http://www.cygwin.com/ , cd to directory where the sources are, and run the make command.
On Linux, cd to the sources directory and run the make command.
*solved* ...
a1exander said:
(Im on Linux Ubuntu)
Hm..
First I forked the FreeXperia directory, cloned it to my home directory. Then I cd it in my terminal by running this code:
cd /home/alexander/FreeXperia/android-cm7/device/se/x10/libgralloc
Then I write "make" and press enter. (I have installed make via Synaptic package manager)
Then I get this error message:
make: *** No targets specified and no makefile found. Stop.
..
Please help, what have I done wrong?
Click to expand...
Click to collapse
yes thats expected as there is no native make file..
may be try renaming that android.mk to 'make' or 'makefile' i dont remember which one works
*solved* ...
a1exander said:
Iv'e already tried that, same error though. This drives me insane..
Click to expand...
Click to collapse
well better insane than impotent that i allways say...
sorry for slow upload but some things are private tools w/o any help or error handlers etc so i have to adjust them little bit.
plus custom kernel toolkit still in w.i.p becouse split boot image / join boot image is being ported to c#
thought i should bump this up...
Chumby_666 has posted:
update-script to edify script converter
for converting amend syntax update-script to edify syntax updater-script (required for xRecovery v1.0.0)
check 1st post
Thank you Chumby_666 for ur work!!!
DooMLoRD said:
thought i should bump this up...
Chumby_666 has posted:
update-script to edify script converter
for converting amend syntax update-script to edify syntax updater-script (required for xRecovery v1.0.0)
check 1st post
Thank you Chumby_666 for ur work!!!
Click to expand...
Click to collapse
Can you explain how this tool works? I couldnt get it to work.
frost866 said:
Can you explain how this tool works? I couldnt get it to work.
Click to expand...
Click to collapse
gui version added i don't think it is that hard now...
apk manager (backup, install, delete apks on phone )--- link: soon
custom boot image toolkit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
azuzu kitchen --- link: soon
nandroid2pc ( xrecovery backup copier / unpacker to pc) --- link: soon
aZuZu amend syntax update-script to edify syntax updater-script converter
RamDisk Packer for Windows
Nice tools!
Could you explain the bootimage and ramdisk tools?
What are those for?
bitmovel said:
Nice tools!
Could you explain the bootimage and ramdisk tools?
What are those for?
Click to expand...
Click to collapse
it is simple..
i don't have linux. so i made ramdisk tool which allows me and to others to pack ramdisk as tar archive on windows.
custom boot image is replacement of mkbootimg, mkbootfs, tar, gzip, gunzip, cpio it is like gui tool to make boot.img which for now only x10 users can use to load new kernel.
looks really nice.
where can we get boot.img to mess with custom boot image toolkit?
Also, where can I get and use ramdisk to stock ROM? to use the Packager?
Tks
HI!
When I use SIN2IMG, in Vista, the extracted system folder is always with individual files shared. How can I disable that?
It is dificult to delete or move the created files becouse of the confirmation messages :-s
on first question: stock rom doesn't have ramdisk. it has bunch of init.* files on root which you can pack to ramdisk.tar and run same as on froyo, or gb. second part of question i don't get it. on second question that confirmation questions and your vista problems are intended for windows help forum... and sin2img just extracts img part from sin and yaffs2 extracts all as ro on windows..
RAMDisk Tool Final Added. Enjoy!
new version of custom boot image toolkit is up!
minor fixes ...
added image to android logo & android logo to image ( external tools ) ( cygwin again! god damn! )
working on new ramdisk handle procedure ... soon will be fixed
thanks DooMLoRD for finding tools
aZuZu said:
new version of custom boot image toolkit is up!
minor fixes ...
added image to android logo & android logo to image ( external tools ) ( cygwin again! god damn! )
working on new ramdisk handle procedure ... soon will be fixed
thanks DooMLoRD for finding tools
Click to expand...
Click to collapse
Thanks a bundle for all the things, they were indeed a great help.
brilliant work. cheers!
---------- Post added at 01:05 AM ---------- Previous post was at 01:02 AM ----------
aZuZu said:
new version of custom boot image toolkit is up!
minor fixes ...
added image to android logo & android logo to image ( external tools ) ( cygwin again! god damn! )
working on new ramdisk handle procedure ... soon will be fixed
thanks DooMLoRD for finding tools
Click to expand...
Click to collapse
Thanks a bundle for all the things, they were indeed a great help.
brilliant work. cheers!
my anti virus is popup
is it possible to at Unlock bootloader to this app?
christi1992 said:
is it possible to at Unlock bootloader to this app?
Click to expand...
Click to collapse
ok if I understand your question you want to unlock bootloade
why you don't use new flash tool
http://forum.xda-developers.com/showthread.php?t=986692
first you need to have root acces install super user and cwm.. but all that you can do with that flash tool
if your mobile it is posible to unlock, than you will have option "plugin" --> "unlock bootloader" --> "run"
youthisbaka said:
my anti virus is popup
Click to expand...
Click to collapse
Change Antivirus
Hello guys
I have a little problem.
I builded kernel, but i have got only image and Zimage.
How can i extract ramdisk (for mkbooimg) ? Thanks
gigitux said:
Hello guys
I have a little problem.
I builded kernel, but i have got only image and Zimage.
How can i extract ramdisk (for mkbooimg) ? Thanks
Click to expand...
Click to collapse
I usually do that using dsixda's Android Kitchen
or I leave the zImage as it is, and flash it with some tools (flashable zip that already made to flash zImages)
omarainea said:
I usually do that using dsixda's Android Kitchen
or I leave the zImage as it is, and flash it with some tools (flashable zip that already made to flash zImages)
Click to expand...
Click to collapse
I can't :'(
Please test this, it would kernel 3.1 :|
Image: http://www.mediafire.com/download/o9907fm1q7leq58/Image
Zimage: http://www.mediafire.com/download/g16fszrme64g344/zImage
Thanks
Install p7zip-full package. Then the kernel from which you need ramdisk, just do this- 7z e kernel_name.elf
It'll give 3 files, 0(zImage), 1(Ramdisk), 2(cmdline).
Cheers,
AJ
Abhinav2 said:
Install p7zip-full package. Then the kernel from which you need ramdisk, just do this- 7z e kernel_name.elf
It'll give 3 files, 0(zImage), 1(Ramdisk), 2(cmdline).
Cheers,
AJ
Click to expand...
Click to collapse
Yep, i try, but i have black screen when boot smarthphone.
Perhaps i do an error....
gigitux said:
Yep, i try, but i have black screen when boot smarthphone.
Perhaps i do an error....
Click to expand...
Click to collapse
As far as i know, tearing down kernel with 7zip (or similar) breaks symlinking. I've read that somewhere, don't remember where. Either way, it breaks something. You could unpack kernel.elf with Flashtool, it will give you image, ramdisk.gz, and maybe file called cert or 3 (it depends). If kernel is boot.img instead of kernel.elf, just rename it to kernel.elf.
if you need help on packing/repacking kernel or ramdisk, PM me, I will help you as much as I can.
evildev said:
As far as i know, tearing down kernel with 7zip (or similar) breaks symlinking. I've read that somewhere, don't remember where. Either way, it breaks something. You could unpack kernel.elf with Flashtool, it will give you image, ramdisk.gz, and maybe file called cert or 3 (it depends). If kernel is boot.img instead of kernel.elf, just rename it to kernel.elf.
if you need help on packing/repacking kernel or ramdisk, PM me, I will help you as much as I can.
Click to expand...
Click to collapse
There are links for download Image and zImage.
gigitux said:
Hello guys
I have a little problem.
I builded kernel, but i have got only image and Zimage.
How can i extract ramdisk (for mkbooimg) ? Thanks
Click to expand...
Click to collapse
Reported!
This should be in Q&A section not in Development section! REPORTED!
Anyway, you can use championswimmer's Android Kernel Kitchen to extract your kernel for getting zImage, ramdisk and the contents of the ramdisk :good:
Garcia98 said:
This should be in Q&A section not in Development section! REPORTED!
Anyway, you can use championswimmer's Android Kernel Kitchen to extract your kernel for getting zImage, ramdisk and the contents of the ramdisk :good:
Click to expand...
Click to collapse
It won't work. If you want just to extract use flashtool. Unpacking with 7-zip will destroy symlinks and packing again will never work. To use flashtool rename boot.img to boot.elf. Choose Tools>Extractors>Elf and choose your boot.elf file you renamed previously. Then press dump and close. It should be in the same folder with the boot.elf file. (boot.elf was always a renamed boot.img file ) BTW wrong section
Andrewasth said:
It won't work. If you want just to extract use flashtool. Unpacking with 7-zip will destroy symlinks and packing again will never work. To use flashtool rename boot.img to boot.elf. Choose Tools>Extractors>Elf and choose your boot.elf file you renamed previously. Then press dump and close. It should be in the same folder with the boot.elf file. (boot.elf was always a renamed boot.img file ) BTW wrong section
Click to expand...
Click to collapse
I said that to OP and he gave me links to his zImage and image.
I don't possess great knowledge concerning android, but I wan't to help if someone is stuck, give instructions, etc. But to do someone else's work, well...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Andrewasth said:
It won't work. If you want just to extract use flashtool. Unpacking with 7-zip will destroy symlinks and packing again will never work. To use flashtool rename boot.img to boot.elf. Choose Tools>Extractors>Elf and choose your boot.elf file you renamed previously. Then press dump and close. It should be in the same folder with the boot.elf file. (boot.elf was always a renamed boot.img file ) BTW wrong section
Click to expand...
Click to collapse
I'm pretty sure that championswimmer's tool works, because I used it just a week ago to extract a kernel and it worked like a charm
However, Flashtool method is OK too
Garcia98 said:
I'm pretty sure that championswimmer's tool works, because I used it just a week ago to extract a kernel and it worked like a charm
However, Flashtool method is OK too
Click to expand...
Click to collapse
Nah, it doesn't. But we can use 7z e kernel.elf and then extract ramdisk from champ's kernel kitchen so it'll not break the symlinks.
Cheers,
AJ
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Universal Tool
Features:
Universal tool - tool for android ROM and kernel developers. It's like a android kitchen;
This tool written on C programming language
Work on dedicated working folder, that allows feel comfortable, when you working.
Unzipping ROM's (everyone. CyanogenMod based, AOSP Based, MiUI and etc...)
Deodexing apk's, if you have .odex, you can quickly get rid of it.
Decompiling and compiling apk's. This step very important, if you want add own features (some animation, colors etc.)
Unpacking boot.img and ramdisk. If you want look at "insides" of boot.img and edit some parameters, you need it.
Unpacking system.new.dat and system.img. When you meet ROM's with system.new.dat, you understand me ROM Porters need it too.
Edit build.prop, updater-script.
Add apk of Kernel control.
Debloat ROM. If you have low RAM on device, you need delete some apps. Tool do it for you.
Installing apktool, adb, fastboot. You don't need use google, tool make it for you. Quickly.
Installing SuperSU.
Porting ROM's based on API 5.0 and higher.
Scrennies
Installing and run
For Linux
You must have installed libncurses5, python (2.7 or newer), JDK 1.7 or newer for working tool.
Press "Download", then extract .zip in your home folder;
Rename to Universal_Tool(if you download from GitHub)
Enter to Terminal and enter "cd Universal_Tool/", then "./tool". It's all.
Enjoy!
For Windows
You must have installed 7zip, JDK 1.7 or newer, Python 3.0, notepad++.
Download .zip
Extract to C:\ drive (IMPORTANT);
Rename to Universal_Tool(if you download from GitHub);
Run from tool.exe
Downloads: View attachment Universal_Tool-UT-linux.zip, View attachment Universal_Tool-UT-windows.zip
Sources: https://github.com/AL3X1/Universal_Tool​
Changelog
11.01.17 - v.1.1
Added Fastboot Menu
Added Porting tools
Fixed apktool problem on linux version
Fixed some error's.
Added information about using tool (manual).
* Tool Written by 4L3X (Bl4ck0verlord on xda, Grand_leMon on 4pda)
* Thanks to:
* iBotPeaches - for ApkTool
* JesusFreke - for smali/baksmali
* xpirt - for sdat2img
* osm0sis - for mkbootimg
* Willi Ye - for Kernel Adiutor
* Chainfire - for SuperSU
* Neko.cpp and lolmaxlik - for helping with some questions
* You
* and...
* I am a modest man, but if you want, you can say 'thank you' to me too.
It seems awesome, I will give ot a spin later.
Thank you man for this tool, you make our developers/designers life easier.
Sent from my LG-H918 using Tapatalk
How to extract rom.zip
@Bl4ck0verlord ahhaaa its great bro
its very nice we see a kitchen which work on windows.
hope this kitchen supported sony devices and we can make rom ( 6.0.1 or 7.0 ) for our device
thanks bro
Bimalhort said:
How to extract rom.zip
Click to expand...
Click to collapse
First: create workspace
Second: place archive with your ROM to workspace folder.
Done
I'm not using that tool on Windows 10 x64
Error says : System can not find specified path
Zorbeyd said:
I'm not using that tool on Windows 10 x64
Error says : System can not find specified path
Click to expand...
Click to collapse
Replace tool in C drive. Then rename to Universal_Tool and launch.
Hello
We can not extract the img system.
Ca plant every time (android7)
Really nice tool just needs to be able to recompile system.img. keep up the good work
omnikam said:
Really nice tool just needs to be able to recompile system.img. keep up the good work
Click to expand...
Click to collapse
+ 1
Hi, thanks for the tool. I want add spanish language to miui 8 china developer rom but i don't know how. Is possible with this tool?
Hi
Good Tool
Really good Tool but can u give me little bit guide for using it
Thank you
Not on my pc for a while but next weekend... Are binaries updated? Smali, su, oat2odex etc? Or can we update them?
Rcv
Good work....
?
I keep getting this- the directory name invalid.
i got this error while trying extract boot.img
What you want?: 3
1 file(s) copied.
The directory name is invalid.
boot.img ready. Press 'Enter'to continue.