Code:
Your Xperia L does NOT have to be rooted.
Your Xperia L does NOT have to be bootloader unlocked.
This does NOT re-lock a SIM unlocked phone (unlocking is ONCE and PERMANENT).
This does NOT unlock your bootloader.
{
"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"
}
C2104_15.0.A.2.17 R10A_Generic IN : https://drive.google.com/file/d/0B155c3sEjlyjeDBBRXczNkxEcG8/edit?usp=sharing
C2104_15.3.A.0.26-R10A_Generic IN : https://drive.google.com/open?id=0B155c3sEjlyjR3VnVnYwNWs2Qjg&authuser=0
C2104_15.3.A.1.14_R10A_Generic IN : https://drive.google.com/open?id=0B155c3sEjlyjU3dVSFhUb3Z1eVk&authuser=0
• .36 FW Stock Kernel by @jayaura : Link
My Blog Link : Click Me !!
Other threads related to Firmwares : here
If this thread helped and want to thank me !! Press that yellow thank button.
Navneet Suresh said:
Hey guys as i told you i came up with stock ROM of Xperia L :laugh::good::highfive: [C2105]
- Why do you need Stock Rom ?
Most of the time its is needed for restoring bricked devices/Restore device again to working states.
So First head here to learn to use Flashtool [Use full to people like me having there first Xperia Device]
After learnin' just flash it up and get back stock rom running :good: :highfive:
Code:
[Mirror] https://docs.google.com/file/d/0B155c3sEjlyjNEFtVHFwQkJlakU/edit?usp=sharing
Code:
Original https://docs.google.com/file/d/0B_d8uWGbkaetZjlGTVJPcmVRTzg/edit?usp=sharing
Other Stock Rom Link [Different Version] XDA LINK Credits : allenwalker1998 & xperiafirmware.com & Google
If this thread helped you just press thanks: It encourages me
Click to expand...
Click to collapse
How will you flash rom without CWM?
Sent from my Xperia L C2104 using xda-premium
Raj joshi said:
How will you flash rom without CWM?
Sent from my Xperia L C2104 using xda-premium
Click to expand...
Click to collapse
Flashtool
Just like Samsung has Odin and LG has KDZ Updater, Sony has Flashtool
use Flash tool
Raj joshi said:
How will you flash rom without CWM?
Sent from my Xperia L C2104 using xda-premium
Click to expand...
Click to collapse
See my guide here for using flashtool.
nolinuxnoparty said:
Flashtool
Just like Samsung has Odin and LG has KDZ Updater, Sony has Flashtool
Click to expand...
Click to collapse
yeah you are right nolinuxnoparty
Navneet Suresh said:
Hey guys as i told you i came up with stock ROM of Xperia L :laugh::good::highfive: [C2105]
Click to expand...
Click to collapse
THX for stock :good:
wich region is this stock Rom? C2105_15.0.A.1.31_CE.ftf --> CE=CentralEuropa?
heross said:
THX for stock :good:
which region is this stock Rom? C2105_15.0.A.1.31_CE.ftf --> CE=CentralEuropa?
Click to expand...
Click to collapse
Its Central Europe 1 Generic CE1 1272-2161 15.0.A.1.31 R3A
boot.img
Can you provide boot.img please?
jayaura said:
Can you provide boot.img please?
Click to expand...
Click to collapse
Boot.img cannot be provided from stock rom because it has boot.sin flash whole stock rom
Navneet Suresh said:
Boot.img cannot be provided from stock rom because it has boot.sin flash whole stock rom
Click to expand...
Click to collapse
Thats fine. But we can do it, right? We can extract the sin file using Flashtool, extract kernel and ramdisk out of it, and then repack them again using mkbootimg?
I just came to know about it lately
oh !!
jayaura said:
Thats fine. But we can do it, right? We can extract the sin file using Flashtool, extract kernel and ramdisk out of it, and then repack them again using mkbootimg?
I just came to know about it lately
Click to expand...
Click to collapse
Hmm then have you made stock kernel ?? If yes PM me the stock boot.img link make sure it is working, i will add it to my thread and credit you
Navneet Suresh said:
Hmm then have you made stock kernel ?? If yes PM me the stock boot.img link make sure it is working, i will add it to my thread and credit you
Click to expand...
Click to collapse
I'm working on it, but try one failed, I want to compile those tools (unmkbootimg) from scratch, for which I need to download GBs of android source. Right now its my net is slow, and expensive too. So waiting for a good connection. I'll send you the stuff once I'm done.
Hmm
jayaura said:
I'm working on it, but try one failed, I want to compile those tools (unmkbootimg) from scratch, for which I need to download GBs of android source. Right now its my net is slow, and expensive too. So waiting for a good connection. I'll send you the stuff once I'm done.
Click to expand...
Click to collapse
Send me when you can there's no urge take your time and if u r successful teach me the trick to do it :highfive:
Navneet Suresh said:
Send me when you can there's no urge take your time and if u r successful teach me the trick to do it :highfive:
Click to expand...
Click to collapse
Infact, I just did! Hail Rachit Rawat. Those tools I needed where put up in his git repo! So he saved my GBs of downlaod. I'll now PM you the boot.img. That would be from the .36 firmware. Put it where you like
Its damn easy to create it though.
1) Extract stock FTF file using some archiver. Its a just a zip archive. You'll now get a lot of sin files, in which kernel.sin is what we need
2) Open Flashtool, go to Tools --> Sin Editor
3) Extract it, you'll get one file kernel.elf.
4) In Flashtool again, go to Tool--> Extractors --> Elf. Select the kernel.elf that was created (in the same folder where you placed kernel.sin, see the info in Flashtool
5) Now you have two files, one is the ramdisk, and other the kernel. You can identify it from its name.
6) Download mkbootimg from Rachit's git repo https://github.com/rachit-rc96/boot-tools
6) Place all your files ( ramdisk, kernel and mkbootimg) in one directory. Open up a terminal ( I hope you are on linux, else get cygwin )
7) type
Code:
./mkbootimg --kernel kernel.elf.Image --ramdisk kernel.elf.ramdisk.gz -o boot.img --base 0x80200000 --ramdisk_offset 0x02000000 --cmdline "console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3" --pagesize 4096
8) now you have boot.img in the same folder!
The one I created did run on my xperia L. However, there was some lag. I believe this is because I have some tweaks done with remaining part of the existing stock .36 firmware, which the stock kernel dont like
Anyways the extended stock kernel must be better than this one!
Error
jayaura said:
Infact, I just did! Hail Rachit Rawat. Those tools I needed where put up in his git repo! So he saved my GBs of downlaod. I'll now PM you the boot.img. That would be from the .36 firmware. Put it where you like
Its damn easy to create it though.
1) Extract stock FTF file using some archiver. Its a just a zip archive. You'll now get a lot of sin files, in which kernel.sin is what we need
2) Open Flashtool, go to Tools --> Sin Editor
7) type
Code:
./mkbootimg --kernel kernel.elf.Image --ramdisk kernel.elf.ramdisk.gz -o boot.img --base 0x80200000 --ramdisk_offset 0x02000000 --cmdline "console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3" --pagesize 4096
8) now you have boot.img in the same folder!
Anyways the extended stock kernel must be better than this one!
Click to expand...
Click to collapse
I was tryin to compile a .31 FW stock kernel and error came "Cannot execute binary file" Using Cygwin on Win 7
Navneet Suresh said:
I was tryin to compile a .31 FW stock kernel and error came "Cannot execute binary file" Using Cygwin on Win 7
Click to expand...
Click to collapse
Thats why I dont recommend Cygwin. Get out of your comfort zone and explore the wild world of linux. That will only help you become more cool I think the error is because your file system doesnt support linux permissions.
Navigate to the directory where you have the executables and try this:
Code:
chmod +x ./mkbootimg
Now try executing them again.
I havent used cygwin, and you might find help regarding that elsewhere in the forum or, well, google
i Love LinuX
jayaura said:
Thats why I dont recommend Cygwin. Get out of your comfort zone and explore the wild world of linux. That will only help you become more cool I think the error is because your file system doesnt support linux permissions.
Navigate to the directory where you have the executables and try this:
Code:
chmod +x ./mkbootimg
Now try executing them again.
I havent used cygwin, and you might find help regarding that elsewhere in the forum or, well, google
Click to expand...
Click to collapse
I love linux but the problem is only i will be using it i had tried to partition the linux and win but my HDD failed,
Edit it didnt work
Dont cygwin!
Navneet Suresh said:
I love linux but the problem is only i will be using it i had tried to partition the linux and win but my HDD failed,
Edit it didnt work
Click to expand...
Click to collapse
I just realized cygwin is not designed to "emulate" native linux applications. You need to compile them for windows. So if you want mkbootimg to run in windows in cygwin, download AOSP source, and build the tools for yourself.
So you're better off using linux itself...
oh !! I see
jayaura said:
I just realized cygwin is not designed to "emulate" native linux applications. You need to compile them for windows. So if you want mkbootimg to run in windows in cygwin, download AOSP source, and build the tools for yourself.
So you're better off using linux itself...
Click to expand...
Click to collapse
i got another method using Android Kitchen i am now tryin to make a stock kernel with CWM
Can I install it on my C2014?
Related
Hello Viewers! I am Rohan Taneja, here with completely re-written guide to Port MTK65xx Roms.
I had left MTK development since a year and I finally got another MTK device to carry with it again.
{
"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"
}
So, Many Of You May be MTK Device User than you are at right place to fill your device with many awesome roms!
Note: Android ONE devices (MT6582 SoC) use Google's device tree, meaning they differ on everything with all the other MediaTek devices (even the ones with the same SoC , MT6582), as per @superdragonpt told us
Requirements:
A MTK powered device
USB Cable
Usable Brains :cyclops:
Knowledge about Flashing & Taking Logs :angel:
Stock Firmware (from manufacturer) & Port Firmware (matching specification of your device)
Custom Recovery installed on device
Porting Tips
Choose Custom ROM from a device matching same resolution to reduce App Size related bugs
This Guide Applies to
MT6577 to MT6577, vice-versa
MT6589 to MT6589, vice-versa
MT6572 to MT6572, vice-versa
MT6582 to MT6582, vice-versa
Note: Try it at your own risk, and don't complaint any developer or XDA if any mishap takes place. :good:
TUTORIAL:Starting with the tutorial, I request you to follow every single step written below to prevent any kind of problem in flashing and causing bootloop. I also dare you to take a nandroid backup of your current rom you are using.
Get. Set. Go.
Step 1 : Patching System Folder for the port patch.First of all make a folder named "Port_Patch" and setup all the folder as shown in the images below.
Now, in Port_Patch make system folder in which make folders, "bin" "etc" "lib" "usr" "vendor" "xbin" (without ")
In folder "bin" copy pq & vold from your stock rom
In folder "etc" copy "bluetooth" "firmware" "wifi" "apns-conf.xml" "vold.fstab" "vold.fstab.nand"
In folder "lib" copy files as shown in the image
In folder "usr" copy usr/keylayout/Generic.kl
In folder "vendor" all the files
In folder "xbin" copy "libmnlp_mt662x" (x - '0' or '8') from stock
System has been patched, copy this /system to patch the /system of port ROM.
Step 2: Patching the boot.img of the port rom.This is bit tricky but can be done easily.
So, first of download this little tool, to unpack & repack your boot.img - MTKbootimg.zip - tested on Windows 7 & above platform
Extract the Tool and you will get two folders named "stock" & "port"
Copy boot.img's respectively from stock rom in "stock" folder & from port rom to "port"
Unpack both boot.img repectively and they may look like this.
From stock copy "kernel" to port folder and just replace it.
Now, repack it, new file named "boot-new.img" will be generated.
Copy "boot-new.img" to port Rom Folder.
Delete existing "boot.img" and rename "boot-new.img" to "boot.img"
Now, your boot.img is patched, proceed to last step.
Step 3: Modifying updater-script to install ROM accordingly.
So, it's the last step before flashing the rom. Now lets fix it.
First, you have to know your device mount points, that can be tracked using MTKDroid Tool or check them in stock rom updater-script.
I have my flashable stock rom so I will get mount points from it.
As show in the image, my stock updater have different mount point for system & data while port have different.
Now, replace "mmcblk0pX" (X - no. for the mount) from stock to port as designated for the partition.
Now Save the updater-script.
Finally, the ROM is ready to flashed.
Step 4: Compressing & Flashing the ROM.
Now, the rom is ready to be packed and flashed.
Simply get to the main directory with META-INF, system, boot.img, etc files.
Select all the files and compress them to zip. Select the compression ratio as you want.
After compressing copy the ROM into root of sdcard
Enter Custom Recovery, wipe data & Cache
Flash the ROM.zip wait till it completes.
Wait till it boots, or else take log using ADB logcat. (Hint: If LED light blinks, the rom is booting)
FOR Fixes Proceed to next post and find out the way to tackle and fix the bugs.
Fixing ROM issues
Finally Ported a Custom ROM. Now, time to kill out some bugs.
Its all about making the build stable for personal as well as others to use it.
Leave the files if not there in your System
Let's get started:
Bootloop? :crying:
Replace following files(from stock to port):
Code:
[LIST]
[*]libandroid_runtime.so
[*]libandroid_servers.so
[*]libmedia_jni.so
[*]libsync.so
[*]If possible try modifying framework.jar "\smali\com\android\server" (copy from stock)
[/LIST]
Camera Not Working?
Replace following files(from stock to port):
Code:
[HIDE][LIST]
[*]lib3a.so
[*]liba3m.so
[*]libacdk.so
[*]libaudioflinger.so
[*]libc.so
[*]libcam.camadapter.so
[*]libcam.campipe.so
[*]libcam.camshot.so
[*]libcam.client.so
[*]libcam.paramsmgr.so
[*]libcam.utils.so
[*]libcam_camera_exif.so
[*]libcamalgo.so
[*]libcamdrv.so
[*]libcamera_client.so
[*]libcamera_jni_eglfence.so
[*]libcamera_metadata.so
[*]libcameracustom.so
[*]libcameraservice.so
[*]libgn_camera_feature.so
[*]libexif
[*]libfeatureio.so
[*]libfrsdk.so
[*]libft.so
[*]libgcomm_jni.so
[*]libgoggles_clientvision.so
[*]libgui.so
[*]libimageio.so
[*]libja3m.so
[*]libjni_mosaic.so
[/LIST]
Thanks To [I]Shikar A[/I][/HIDE]
[B]Init.rc Fix:[/B]
[HIDE]Init.rc(present in the ramdisk of boot.img), find for code #Camera in stock boot.img. Copy it and replace from stock init.rc and replace in the port init.rc
[IMG]http://s27.postimg.org/4ucj34cwj/initrc_cam.png[/IMG][/HIDE]
Wlan not working properly?
Code:
Check wlan.chip in stock like:
[HIDE][IMG]http://s30.postimg.org/myaya0sxt/Untitled.png[/IMG]
fmradio.driver.chip=x (if mt6620 then x=1, if mt6628 then x=3)
Change the above codes accordingly in updater-script
Replace the version in port from the one in stock[/HIDE]
(Replace from stock to port)
libbluetooth_mtk.so
libbluetoothem_mtk.so
GPS, unstable or not working?
(Replace from stock to port)
Code:
xbin/libmnlp
Media Player problem?
(Replace from stock to port)
Code:
libdpframework.so
libcodecvdrv.so
Sensors not working properly?
(Replace from stock to port)
Code:
libsensorservice.so
SD Card not working or mounting?
Code:
In the framework-res.apk of your port, replace /res/xml/storage_list.xml from stock one.
USB not mounting your device?
Code:
Unpack your boot.img replace init.usb.rc from ramdisk by stock boot.img init.usb.rc
This tutorial worked for porting MIUI, Baidu, Vibe UI, LeWa OS, AOSP based rom from different device to my MT6589 of same hardware.
Credits:
Special Thanks to @yuweng (for starting his main MTK porting thread and his great works)
XDA-Developers being one of the best place for Android Development
Other Developers for helping in fixing most the issues.
just wanna ask..is it ok if i dont copy the srec folder cause i cant find it..also yhe meta-inf folder as i only have the system.img of my base rom
iel0000 said:
just wanna ask..is it ok if i dont copy the srec folder cause i cant find it..also yhe meta-inf folder as i only have the system.img of my base rom
Click to expand...
Click to collapse
If You Don't Have "srec" folder no need to worry but for system.img you need to extract the img by ext4 method:
http://forum.xda-developers.com/showthread.php?t=2285831
A N D Y said:
If You Don't Have "srec" folder no need to worry but for system.img you need to extract the img by ext4 method:
http://forum.xda-developers.com/showthread.php?t=2285831
Click to expand...
Click to collapse
how about theses files?
CERT.RSA
CERT.SF
MANIFEST.MF
i dont have them cause i dont have a flashable stock rom..
iel0000 said:
how about theses files?
CERT.RSA
CERT.SF
MANIFEST.MF
i dont have them cause i dont have a flashable stock rom..
Click to expand...
Click to collapse
Don't Worry Try The one in the Ported Rom!
cant also find these
com.google.android.media.effects.jar
com.google.android.media.effects.xml
sorry for the noob questions..i just want to port a rom to my device as we dont have developers
it worked!
i ported an miui from newman n1, the ics 4.0.4 with no bugs to my cherry mobile blaze / Ming Ren A2 clone.
btw, this is not a dual sim display miui, i need to go to settings anytime i wan to use the other sim.
anyone who knows where to get a dual sim display miui?
xjammetx said:
it worked!
i ported an miui from newman n1, the ics 4.0.4 with no bugs to my cherry mobile blaze / Ming Ren A2 clone.
btw, this is not a dual sim display miui, i need to go to settings anytime i wan to use the other sim.
anyone who knows where to get a dual sim display miui?
Click to expand...
Click to collapse
what boot.img did you use? stock from cherry mobile?
iel0000 said:
what boot.img did you use? stock from cherry mobile?
Click to expand...
Click to collapse
Don't Try boot.img(Kernel) from the port rom or you'll brick your device!
iel0000 said:
cant also find these
com.google.android.media.effects.jar
com.google.android.media.effects.xml
sorry for the noob questions..i just want to port a rom to my device as we dont have developers
Click to expand...
Click to collapse
Those Files You Can't Find In port just leave that!
A N D Y said:
Don't Try boot.img(Kernel) from the port rom or you'll brick your device!
Click to expand...
Click to collapse
can i use stock boot.img from my phone?or do i have to modify it?
Very nice thread, for beginners that want to learn
tried porting miui v5 base on jb 4.1.2
always stock on boot animation
iel0000 said:
can i use stock boot.img from my phone?or do i have to modify it?
Click to expand...
Click to collapse
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
A N D Y said:
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
Click to expand...
Click to collapse
i give up porting miui to my phone and tried porting another rom from amoi n820..it boot but the home key is not working..i already used Generic.kl from my device stock rom but it still dont work can you help me plss?
edit : i finally got it working..thanks for the tut it really help me....
iel0000 said:
what boot.img did you use? stock from cherry mobile?
Click to expand...
Click to collapse
Yep. Dont worry, ill upload it sometime.
A N D Y said:
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
Click to expand...
Click to collapse
how to use the tool?
How to from STOCK
iel0000 said:
how to use the tool?
Click to expand...
Click to collapse
Do you know procedure to Port a STOCK ROM(SP Flash tool format not a CWM) of X device to Y device?
Both are mostly same in specifications except the resolution.
I read in some threads that we can not port a rom from a device which has different resolution ?
Thanks in Advance
iel0000 said:
i give up porting miui to my phone and tried porting another rom from amoi n820..it boot but the home key is not working..i already used Generic.kl from my device stock rom but it still dont work can you help me plss?
edit : i finally got it working..thanks for the tut it really help me....
Click to expand...
Click to collapse
what phone do you have btw?
yo kumpare!
I just made a zImage out of htc source code .
The source is for mec_dwg variant of HTC One M8 Ace --- htc_Asia
I have Htc One E8 dual sim M8Sd mec_dwgl device from india, i'm not sure whether the above zImage is compatible, time will tell !
I need anybody's help making a boot.img because I dont know where to get the ramdisk.
Also I request anybody to help me
-integrate wifi modules
-integrate wp_mod.ko for disabling system write protection
-making an insecure kernel
Thanks in advance.
iamsuperuser said:
I just made a zImage out of htc source code .
The source is for mec_dwg variant of HTC One M8 Ace --- htc_Asia
I have Htc One E8 dual sim M8Sd mec_dwgl device from india, i'm not sure whether the above zImage is compatible, time will tell !
I need anybody's help making a boot.img because I dont know where to get the ramdisk.
Also I request anybody to help me
-integrate wifi modules
-integrate wp_mod.ko for disabling system write protection
-making an insecure kernel
Thanks in advance.
Click to expand...
Click to collapse
Just get the ramdisk from your current boot.img.
Pull the modules from your current ROM.
If building from source, there's no need to use wp_mod.ko. Just disable write protection in the source when you build the kernel.
Making the kernel insecure is a ramdisk tweak. Just change ro.secure=1 to ro.secure=0 in the default.prop.
I'm locked and unrooted
And I don't have my boot.img , where do I get it from??
Anyway Can I use ramdisk from M8Sw variant on M8Sd ??
By Modules from my Rom u mean the whole system/lib/modules folder???
Thanks for the system write protection fix, can you find a similar fix for ext_sd card write protection too .
I know the one with platform.xml , I'm hoping you could find in the source itself.
iamsuperuser said:
I'm locked and unrooted
And I don't have my boot.img , where do I get it from??
Anyway Can I use ramdisk from M8Sw variant on M8Sd ??
By Modules from my Rom u mean the whole system/lib/modules folder???
Thanks for the system write protection fix, can you find a similar fix for ext_sd card write protection too .
I know the one with platform.xml , I'm hoping you could find in the source itself.
Click to expand...
Click to collapse
Pull the boot.img from your device using dd, i.e.
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
Then you can use Android Image Kitchen to unpack it. You can then replace the zImage with your built one, repack, and you'll have a working boot.img. Or, you can use AnyKernel 2.0 to just replace the zImage in your existing ROM, add any ramdisk tweaks you'd like, and flash in recovery, which will preserve your current ramdisk.
And yes, by modules from your ROM, I mean your system/lib/modules folder.
There is no kernel fix for the writing to external SD - that's an Android thing. The only place to "fix" it is in platform.xml, which you already know about.
And I don't know anything about the differences between these variants, so I couldn't tell you what will or won't work on any of them. You're just going to have to test it and see for yourself.
Nice discussed. Will monitor to learn from you guys... Thanks
One dumb q'
Do I need to s-off to flash boot.img or unlock via htcdev is enough??
Google told me to s-off only if I have to flash boot.img through recovery otherwise I can flash boot.img through adb even on s-on
Pls clarify
iamsuperuser said:
One dumb q'
Do I need to s-off to flash boot.img or unlock via htcdev is enough??
Google told me to s-off only if I have to flash boot.img through recovery otherwise I can flash boot.img through adb even on s-on
Pls clarify
Click to expand...
Click to collapse
You can fastboot flash a boot.img while S-ON, as long as your bootloader is unlocked.
{
"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"
}
Ok Finally made it. I'm using it on my Htc One E8 i.e. M8Sd Htc__038 htc_Asia mec_dwgl
I would request somebody to test it, preferably from India, since this effort is toward Indian users.
I used System write protection fix in the zImage while building the kernel so there is no need to use wp_mod.ko
Please backup your kernel first, I am not responsible if this kernel bricks your device, do it at your own risk
boot.img
If this works , anymore help and ideas are most welcome :highfive:
@Captain_Throwback
Can THIS be included in the zImage like the sys r/o fix ?
If yes, pls tell me how ??
iamsuperuser said:
@Captain_Throwback
Can THIS be included in the zImage like the sys r/o fix ?
If yes, pls tell me how ??
Click to expand...
Click to collapse
I'm sure if you just look at @flar2's source, you can see where/how he added sweep gestures.
Captain_Throwback said:
I'm sure if you just look at @flar2's source, you can see where/how he added sweep gestures.
Click to expand...
Click to collapse
I tried , all I learned that its a .c file similar to the ones in the modules folder of kernel source folder, maybe this one goes there and I just have to make -j8 to zImage.
But I could really use your help to be sure about how to add and compile it.
iamsuperuser said:
I tried , all I learned that its a .c file similar to the ones in the modules folder of kernel source folder, maybe this one goes there and I just have to make -j8 to zImage.
But I could really use your help to be sure about how to add and compile it.
Click to expand...
Click to collapse
A better person to ask would be @flar2.
I've had issues compiling the standalone modules.
cool
Will try to flash your kernel today.
update -
flashed the kernel successfully. no issues so far. Can you tell what all changes are there in this kernel?
There are some text saying "this build is for development purpose only... blah blah" with red font on htc logo page on phone restart.
swordfish2009 said:
cool
Will try to flash your kernel today.
update -
flashed the kernel successfully. no issues so far. Can you tell what all changes are there in this kernel?
There are some text saying "this build is for development purpose only... blah blah" with red font on htc logo page on phone restart.
Click to expand...
Click to collapse
Nothing fancy, just the system write protection is off by default so there is no need to use wp_mod.ko
The red text is normal because the kernel is insecure.
With this kernel it is very easy to root and stay rooted.
I'm not a developer but I'm still learning from other threads and hopefully I will add some more features.
Thanks for testing.
swordfish2009 said:
cool
Will try to flash your kernel today.
update -
flashed the kernel successfully. no issues so far. Can you tell what all changes are there in this kernel?
There are some text saying "this build is for development purpose only... blah blah" with red font on htc logo page on phone restart.
Click to expand...
Click to collapse
The red text comes for me also and I'm on stock sense with stock kernel. I only flashed twrp recovery after unlocking bootloader and rooting the phone.
gregferns said:
The red text comes for me also and I'm on stock sense with stock kernel. I only flashed twrp recovery after unlocking bootloader and rooting the phone.
Click to expand...
Click to collapse
It's not at all a problem, just read what it says.
If ro.secure=0 in kernel or recovery then the red text appears
You can check the default.prop by unpacking your imgs with Android Image Kitchen
iamsuperuser said:
@Captain_Throwback
Can THIS be included in the zImage like the sys r/o fix ?
If yes, pls tell me how ??
Click to expand...
Click to collapse
After looking into this further, you can't build this into the kernel as it is, but you can compile it as a module (much like wp_mod) and then insmod it to load at startup.
EDIT: Here are the instructions for doing that.
Captain_Throwback said:
After looking into this further, you can't build this into the kernel as it is, but you can compile it as a module (much like wp_mod) and then insmod it to load at startup.
EDIT: Here are the instructions for doing that.
Click to expand...
Click to collapse
What's the difference between compiling it and just downloading the module and using it ??
iamsuperuser said:
What's the difference between compiling it and just downloading the module and using it ??
Click to expand...
Click to collapse
If you compile it, using your kernel source as a base, no hex-editing needs to be done to the module for it to load. The pre-compiled module will likely need to be hex-edited to insmod properly, if it works at all.
iamsuperuser said:
It's not at all a problem, just read what it says.
If ro.secure=0 in kernel or recovery then the red text appears
You can check the default.prop by unpacking your imgs with Android Image Kitchen
Click to expand...
Click to collapse
True its not at all a problem.. I was just mentioning that even i get it....
CWM nandbackup files extractor ( .img/ .tar)
Here are the few things/ questions raised
The tool has been upgraded and you can get them here Utility tool
How do i extract the data.ext4.tar ?
How to combine all the *.ext4.tar *.ext4.tar.a , *.ext4.tar.b, *.ext4.tar.c ?
How to get my applications / data from the backup filesof CWM ?
Don't worry for the above question you are facing. This tool will help you out.
Requirements
Java JDK :good:
Need Patience :silly:
How to use
Extract the tool.zip and follow up the pics and your work is done
{
"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"
}
Hope this tool may help some one . and Don't Forget to hit thanks button. have fun
Download
You can also extract the data.img , system.img files on by placing the files to image files folder
Here is the download of the tool at bottom this post
Have fun
Perfect tool Thank you for your hard Word. Now everthing is very easy
The tool which I have been waiting for...works like charm!!
Thank for providing us this tool.
Gonna try to make GUI for this tool.
needed from ages
well first of all congrats for this wonderful tool it was much needed right from the beginning. plus i like your profile pic lol its my fav "KICK"...
will this work on twrp?
or it has different backup file type?
I just switched to twrp but not yet trying nandroid
Perfect tool!! This is really gonna help me with my custom rom instead of trying to copy the /system files one by one to my internal storage.
i'll be waiting for os x version as well (since i don't always run windows)
great tool btw
and congrats for making it to the portal
Error:'Tar' is not recognized as an internal or external command. And also 'cat'.
Where do these commands exist? are they exe files present somewhere in the java jdk folder?
Before you ask. Yes i have installed java jdk.
Do I have to setup the environment variables?
LastStandingDroid said:
i'll be waiting for os x version as well (since i don't always run windows)
great tool btw
and congrats for making it to the portal
Click to expand...
Click to collapse
sure i will do that when i am free..........
zamzameir said:
will this work on twrp?
or it has different backup file type?
I just switched to twrp but not yet trying nandroid
Click to expand...
Click to collapse
I haven't tested but there is nothing more difference between the files. hope it works
dattafilthyd said:
Error:'Tar' is not recognized as an internal or external command.
Before you ask. Yes i have installed java jdk.
Do I have to setup the environment variables?
Click to expand...
Click to collapse
the common softwares are 7z / winrar / winzip are minimum requirement ( i have not listed these because these are very commonly used by every user )
Only cwm or twrp too?
venkat kamesh said:
The common softwares are 7z / winrar / winzip are minimum requirement ( i have not listed these because these are very commonly used by every user )
Click to expand...
Click to collapse
All of them are installed bro. (i.e 7z winrar and winzip)
The bat file you've careated is unable to find 'tar' command. Is it necessary that i place it in a particular location like c drive as such.?
['tar' is not recognized as an internal or external command]
suggestions?
EDIT: I used the cygwin terminal to concatenate [cat] the tar files and i was able to open them combined file via 7z and winrar.
code: cat data.ext4.tar data.ext4.tar.a data.ext4.tar.b data.ext4.tar.c > datafull.tar
Thank you.
the_vanya1 said:
Only cwm or twrp too?
Click to expand...
Click to collapse
i havent tested but hope it works good
dattafilthyd said:
All of them are installed bro. (i.e 7z winrar and winzip)
The bat file you've careated is unable to find 'tar' command. Is it necessary that i place it in a particular location like c drive as such.?
['tar' is not recognized as an internal or external command]
suggestions?
Click to expand...
Click to collapse
there is no particular location to be place.... :good:
may be binaries get corrupted try to install this tool :- http://gnuwin32.sourceforge.net/packages/gtar.htm
it would help you out for using this tool
Error:'Tar' is not recognized as an internal or external command
venkat kamesh said:
You can also extract the data.img , system.img files on by placing the files to image files folder
Here is the download of the tool at bottom this post
Have fun
Click to expand...
Click to collapse
you know, this is an excellent utility, will come handy....what I always thought about is, converting andbackup files into flashable zip - say using your tool, you extracted, and then remove or add or made some changes on it, and then converting to flashable zip..., if you make an ultimate utility tool, imaging that you did nandroid backup of your stock ROM with custom recovery, having a tool to extract it (your utility), and then if you wish deodexed it, and then last step put all into CWM flashable zip....now if you combine all this steps, you will end up ultimate best utility tool ever... I f...king even pay or donate for it...
the_vanya1 said:
Error:'Tar' is not recognized as an internal or external command
Click to expand...
Click to collapse
you need to install 7zip/winzip ( any one of them ) read the previous post
please ready the posts so there you get a solution
jazzespresso said:
you know, this is an excellent utility, will come handy....what I always thought about is, converting andbackup files into flashable zip - say using your tool, you extracted, and then remove or add or made some changes on it, and then converting to flashable zip..., if you make an ultimate utility tool, imaging that you did nandroid backup of your stock ROM with custom recovery, having a tool to extract it (your utility), and then if you wish deodexed it, and then last step put all into CWM flashable zip....now if you combine all this steps, you will end up ultimate best utility tool ever... I f...king even pay or donate for it...
Click to expand...
Click to collapse
thank you for your great idea which is very worth
i had finally made that tool which has options like
1. extract data
2.extract system
3.deodex/ signed zip/zipalign
4.odexed /signed zip/zipalign
5.image file extraction
6. signer
7. odex/deodex invividual
the odex/deodex have different options like
if you extract the system file. it ask an option to odex/deodex . if you need to deodex that it will continue to deodex / zipalign/ signed which will be worked. and same as with odex..
if you dont have any imagefile extracted . there is an option that you can pull from the device and works as same above process
you can sign the zip/zipaline individually as per needed.
hopefully it works on all devices like ( sony, lg, samsung and almost all )
no specification of roms ( every rom is supported )
works for all version of android ( from 2.2 to 4.4.4)
thank you @jazzespresso for this idea
going to post as soon as possible
venkat kamesh said:
thank you for your great idea which is very worth
i had finally made that tool which has options like
1. extract data
2.extract system
3.deodex/ signed zip/zipalign
4.odexed /signed zip/zipalign
5.image file extraction
6. signer
7. odex/deodex invividual
the odex/deodex have different options like
if you extract the system file. it ask an option to odex/deodex . if you need to deodex that it will continue to deodex / zipalign/ signed which will be worked. and same as with odex..
if you dont have any imagefile extracted . there is an option that you can pull from the device and works as same above process
you can sign the zip/zipaline individually as per needed.
hopefully it works on all devices like ( sony, lg, samsung and almost all )
no specification of roms ( every rom is supported )
works for all version of android ( from 2.2 to 4.4.4)
thank you @jazzespresso for this idea
going to post as soon as possible
Click to expand...
Click to collapse
yeah making it work for all devices going to be quit challenging, there are, as you may know, too many odex/deodex tools here in XDA, but none are bug free. In fact, I always end up some kind of error during deodexing, so this part is always painful process no matter what devices you have, and you know people using Windows, Linux, Mac..etc, this puts more complexity to entire process.
but you have to start from somewhere, right?
hopefully, this process of yours grow into some nice utility that combines all other tools into one.:good:
Needless to say, good job and very much appreciated releasing it here in XDA community!
venkat kamesh said:
.....i had finally made that tool which has options........
......going to post as soon as possible.......
Click to expand...
Click to collapse
that's some spread - the menu :good: bring it on!
Already did it sir, and i use winrar
jazzespresso said:
yeah making it work for all devices going to be quit challenging, there are, as you may know, too many odex/deodex tools here in XDA, but none are bug free. In fact, I always end up some kind of error during deodexing, so this part is always painful process no matter what devices you have, and you know people using Windows, Linux, Mac..etc, this puts more complexity to entire process.
but you have to start from somewhere, right?
hopefully, this process of yours grow into some nice utility that combines all other tools into one.:good:
Needless to say, good job and very much appreciated releasing it here in XDA community!
Click to expand...
Click to collapse
m0han said:
that's some spread - the menu :good: bring it on!
Click to expand...
Click to collapse
thank you and here is a pic that i am testing all the things i found no errors and still testing
because it need to be perfect
{
"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"
}
TencentOS is an aftermarket firmware designed by the Chinese company Tencent. Tencent also created the QQ and WeChat IM services.
TencentOS, just like MiUi is not open source. However, Tencent has provided a version of PatchRom for you to use called TOSPlus. I have tested this on the Samsung Galaxy Star Pro. The guide for the TencentOS PatchRom is different than the MiUi and LewaOS and it is written in Chinese only. I will be writing a guide in English so that more people can port this great ROM to their devices.
Pre Steps:
You should Install 2 versions of Java. Version 7, and Version 6.
For Ubuntu and derivatives, type:
Code:
sudo apt-get install openjdk-7-jdk
Now we need the official Java 6.
For Ubuntu and derivatives, type:
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
Be sure to select add when it asks if you want to add the repository or not.
Then, make sure you have all of the required android packages:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip
Note: the above is only for 64-bit. Will update when 32-bit is tested.
------------------------------------------------------------------------------------------------------
Step 1:
Make sure you are on a version of Ubuntu 14.04 or greater (16.04 may or may not work).
Step 2:
Now you need to make a copy of the TencentOS PatchRom. Change to whatever directory you want and Type:
Code:
git clone https://github.com/TOSPlus/TPS
This will make a folder called TPS in whatever directory you were in before. The TPS folder will contain all of the code required to build TencentOS for your device.
Step 3:
Change the directory to TPS and type:
Code:
source build/envsetup.sh
This will initiate the build process.
Step 4:
Next, you build the directory for your device. Type:
Code:
make create brand=put-manufacturer-name device=device-model
Replace "put-manufacturer-name" with your manufacturer and replace "device-model" with your device model.
Step 5:
Next you need to copy a zip file of a ROM you want to use as your base into your device model folder. Name the zip file to ota.zip. Make sure the base ROM is android 4.3 or above.
Step 6:
Now, you configure the build. Type:
Code:
make config device=device-model
Replace device-model with your device's model.
Step 7:
Once you have that done, you need to edit a few files. Those files are misc_info.txt, remove_files.list, tos_system_files.ignore, and build.prop. You can find all of the files underneath the config folder within your device-model folder.
In misc_info.txt, you need to change blocksize, boot_size, recovery_size, system_size, userdata_size, and cache_size to match your device. You can find these in the BoardConfig.mk of your device.
In remove_files.list, you add the files that need to be removed so that TencentOS can function fully. This usually takes quite a bit of trial and error to get correct.
In tos_system_files.ignore, you designate which files should not get edited when you are patching the different services.
In the build.prop, you need to add the TencentOS properties.
example (for the gt-i9500):
ro.qrom.beaconkey=0M000V5PH01B6QQD
ro.qrom.product.device=ja3g
ro.qrom.product.device.brand=samsung
ro.qrom.build.brand=tos
ro.qrom.build.os=android4.4.2
ro.qrom.otapath=/data/media/0
qrom_disposeIcon_enable=1
qrom_permission_enable=1
# ro.qrom.build.version.snflag=ADRQRTOS
ro.qrom.build.version.snver=01
#need edit ro.qrom.build.version.day=151028
ro.qrom.build.version.name=ADRQRTOS01_M
ro.qrom.build.version.number=01151028
ro.qrom.build.version.type=M
#need edit ro.qrom.build.number=3
ro.qrom.build.lc=A1B2C3000D4E5F6
ro.qrom.build.lcid=99
#need edit ro.qrom.build.date=Wed OCT 28 21:01:25 CST 2015
ro.qrom.build.date.utc=1446014851
ro.qrom.build.type=mod
Everything that says need edit, you need to edit for your device specifically.
Step 8:
Copy file_contexts from the boot.img and put in the config folder.
Step 9:
Copy recovery.fstab from the recovery.img of your device to the config folder
Step 10:
Next, you need to extract all of the files from the ota.zip and put them in the correct place. To do that, type:
Code:
make prepare
Step 11:
Now, you can patch your ota.zip. type:
Code:
make patch
If there are any failed patches, you have to patch those smali files manually.
Step 12:
After patching has been done, type:
Code:
make repack
It repacks the jars and frameworks required that TencentOS has edited.
Step 13:
You made it this is the final step. Type:
Code:
make package
It will create a zip file of TencentOS for your device model.
Then you can flash it in a custom recovery and enjoy your new ROM
Here is a video of how to do it: http://forum.xda-developers.com/showpost.php?p=67495578&postcount=75
===========================================================================================
Apps you should manually remove after building (not all may be in your ROM) :
SystemUI.apk
Trebuchet.apk
Dialer.apk
Mms.apk
Contacts.apk
Email.apk
DSPManager.apk
qotaupdater.apk (let's face it, our devices will never get an official update )
Apollo.apk
Launcher3.apk
SetupWizard.apk
VideoEditor.apk
Calculator.apk
Calendar.apk
CalendarProvider.apk
CMFileManager.apk
CMHome.apk
CMWallpapers.apk
DocumentsUI.apk
Gallery2.apk
DownloadProviderUI.apk
HoloSpiralWallpaper.apk
InCallUI.apk
LatinIME.apk (or qime.apk)
LiveWallpapers.apk
LiveWallpapersPicker.apk
LockClock.apk
MagicSmokeWallpapers.apk
PackageInstaller.apk
SoundRecorder.apk
Term.apk
VideoEditor.apk
CMAccount.apk
CMUpdater.apk
Contactsprovider.apk
VoiceDialer.apk
qtheme.apk
ThemeChooser.apk
ThemeProvider.apk
if you dont mind can you please share your device tree
!
manojkumar8552 said:
if you dont mind can you please share your device tree
!
Click to expand...
Click to collapse
You don't actually need a device tree or kernel tree for this, as long as you have a deodexed zip of the ROM you will use as your base, you can build TencentOS.
Here is my github anyways: https://github.com/Qiangong2
Can we port this rom for any device with above mentioned steps
Sent from my XT1022 using XDA-Developers mobile app
surajsj said:
Can we port this rom for any device with above mentioned steps
Sent from my XT1022 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. It even works on Spreadtrum devices
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
Yes. It even works on Spreadtrum devices
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
What are spreadtrum devices. Won't u continue the rom for star pro
Sent from my XT1022 using XDA-Developers mobile app
surajsj said:
What are spreadtrum devices. Won't u continue the rom for star pro
Sent from my XT1022 using XDA-Developers mobile app
Click to expand...
Click to collapse
Spreadtrum devices refers to the processor. Spreadtrum devices use spreadtrum processors, Mediatek devices use Mediatek processors, and Qualcomm devices use Qualcomm processors. Spreadtrum devices are notorious for being hard to develop for as there is not as much information on them as on Qualcomm and Mediatek devices.
Sent from my Q5 using XDA Free mobile app
Ok
Sent from my XT1022 using XDA-Developers mobile app
Qiangong2 said:
Step 6:
Now, you configure the build. Type:
Code:
make config=device-model
Click to expand...
Click to collapse
make config device=device-model
manojkumar8552 said:
make config device=device-model
Click to expand...
Click to collapse
Yup you're right. Added it to original post.
Hello.
I want to ask about something.
Can we enable the navigation bar in build.prop,and is the system fully compatible with it?
Also,has it been tested on Lollipop?
The Marionette said:
Hello.
I want to ask about something.
Can we enable the navigation bar in build.prop,and is the system fully compatible with it?
Also,has it been tested on Lollipop?
Click to expand...
Click to collapse
The notification bar is built into qsystemui.apk. You need to remove the original systemui.apk that you had in the ota.zip after the packaging.
Sent from my Q5 using XDA Free mobile app
Hmmm, I got around 40 errors. Where are the "reject" files put after the command ends?
The errors look like this:
Code:
[ERROR]patching /home/the/roms/tencent/TPS/devices/tos/smali/framework2.jar/smali/com/android/internal/app/ChooserActivity.smali ... fail.
[ERROR] cannot find corresponding target smali file of com/android/internal/app/ChooserActivity.smali
The Marionette said:
Hmmm, I got around 40 errors. Where are the "reject" files put after the command ends?
The errors look like this:
Code:
[ERROR]patching /home/the/roms/tencent/TPS/devices/tos/smali/framework2.jar/smali/com/android/internal/app/ChooserActivity.smali ... fail.
[ERROR] cannot find corresponding target smali file of com/android/internal/app/ChooserActivity.smali
Click to expand...
Click to collapse
There is no reject file as far as I can find. I didn't honestly look too hard though. If you are on Lollipop, I haven't tried it on 5.0 or above. You have to go into the smali file that has an error and manually patch it. Also, I used CM11 as my base. You may need an aosp or cm based rom to be used as your base.
Sent from my Q5 using XDA Free mobile app
is this working for MTK device? tnx
Qiangong2 said:
There is no reject file as far as I can find. I didn't honestly look too hard though. If you are on Lollipop, I haven't tried it on 5.0 or above. You have to go into the smali file that has an error and manually patch it. Also, I used CM11 as my base. You may need an aosp or cm based rom to be used as your base.
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
I am using Cm12.1 as a base. And we have nothing older than CM12.1...
When I was using the FlymeOS Patchtool,if it had errors,it would distinctively show the conflicts in the troublesome files.
But Tencent Patchtool doesn't make a "reject" folder.
I tried searching for the files,and I would get two files found. I open them both in text editors,but there are no conflict lines in there.
Then I tried to just make the package,but it gave me an error mentioning those files which weren't edited.
UnKnoWn.XD said:
is this working for MTK device? tnx
Click to expand...
Click to collapse
It should
Sent from my Q5 using XDA Free mobile app
The Marionette said:
I am using Cm12.1 as a base. And we have nothing older than CM12.1...
When I was using the FlymeOS Patchtool,if it had errors,it would distinctively show the conflicts in the troublesome files.
But Tencent Patchtool doesn't make a "reject" folder.
I tried searching for the files,and I would get two files found. I open them both in text editors,but there are no conflict lines in there.
Then I tried to just make the package,but it gave me an error mentioning those files which weren't edited.
Click to expand...
Click to collapse
Okay. Were any successful at patching?
Sent from my Q5 using XDA Free mobile app
The Marionette said:
I am using Cm12.1 as a base. And we have nothing older than CM12.1...
When I was using the FlymeOS Patchtool,if it had errors,it would distinctively show the conflicts in the troublesome files.
But Tencent Patchtool doesn't make a "reject" folder.
I tried searching for the files,and I would get two files found. I open them both in text editors,but there are no conflict lines in there.
Then I tried to just make the package,but it gave me an error mentioning those files which weren't edited.
Click to expand...
Click to collapse
I think I figured out why it won't work. It won't work if you have the rom with .dat files. You need it open like on 4.4 and below.
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
I think I figured out why it won't work. It won't work if you have the rom with .dat files. You need it open like on 4.4 and below.
Click to expand...
Click to collapse
I made the zip open already,I am not THAT bad. xD
But I hope we are on the same page here. I made sure that my zip wasn't block based,but normal like 4.4 was(I could edit all things inside the zip instead of having one system.DAT image in the zip).
This tool is a part of ADK software, thread can be found here (For summary read Introduction part below). Read Instructions at the end on how to install this.
Click to expand...
Click to collapse
{
"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"
}
Snapshot
Click to expand...
Click to collapse
Introduction
This Utility adds option to right click decompile, compile options for some extensions (like apk, img, dat, br, file_context.bin, payload.bin) so that you don't have to open any kind of kitchen again and again move files there and select options to unpack. See screenshots above you will get an idea about what is it..
Also it's not a separate tool it is a part of ADK. Read Installation and download instructions from below and check 2nd post for usage instructions.
And yes the main part since ADK kitchen is not completely free it works for only 7 days as a trial after that you will have to use demo version which has certain feature disabled. Not to worry this utility will work fine but there will be a pop-up notifying to buy license.
What is ADK?
Well if I've to say, ADK (Android Development Kit) is a complete Windows based GUI application which allows you to edit Android apk files, ROM zips, boot or recovery images, Android Firmware and also to create TWRP/CWM flashable recovery zips easily. It's like a complete Android Kitchen with lots of mods, patches, scripts, templates, rich text editor, etc. like an IDE. For more info visit official thread here.
Click to expand...
Click to collapse
Features
Well here you go,,,
Unpack/Repack APK (including smali), IMG, DAT, BR files.
Generate Java Source for APK.
View APK Info like App name, Package, permissions, icon, etc.
Import App as dependency for system apk.
Support Android 9.0 ROM.
Supported lists are: System, Vendor img, dat, br and Recovery or Boot images)
Suggest me what to add more.. :laugh:
Click to expand...
Click to collapse
Changelog and Known Issues
Changelog as per release 1.1.0.0 (17th January 2019)
*Added: Option to unpack Payload.bin
*Added: Option to convert file_contexts.bin to file_context
*Added: Support for Android 9.0 images.
*Updated: APK decompiling so as to create project for ADK.
Known Bugs
* Unpack option is not showing for .IMG file (on Win8.1 and lower).
Current Fix:- Open CMD and type "contexts d path-to-img" (without quotes).
Click to expand...
Click to collapse
Downloads & Instructions
To use these feature you must have ADK to be installed. So read steps below (noob friendly) in order to get it. If you want to know what is ADK read Introduction Part above.
Step 1: Install ADK
Grab a latest release of the software from above link.
Step 2: Extract the ZIP and install setup.exe as we normally do.
Do not install the software in C:\Program Files or Program Files (x86) folder.
Step 3: Launch ADK from desktop shortcut and go to Help > Plugins & Patches.
Keep your internet connection ON to do this steps.
Step 4: Search for ADK Context [Script] and install it.
First click on Download option then after click on Install it. Installation will be like normal setup file.
Step 5: Once installed you can close ADK and use the plugin.
Click to expand...
Click to collapse
Reserved
Nice tool keep up the good work!
Sent from my Redmi 4X using Tapatalk
can we then recompile say a vendor img after using this tool to unpack?
Xdevillived666 said:
can we then recompile say a vendor img after using this tool to unpack?
Click to expand...
Click to collapse
Yes why not! Just right click on the unpack folder created by the tool and select Encode APK,IMG,DAT,BR option from there
Tool has been updated. To download it open ADK it will notify you which plug-in needs to be updated!
[email protected] said:
Yes why not! Just right click on the unpack folder created by the tool and select Encode APK,IMG,DAT,BR option from there
Click to expand...
Click to collapse
Can't repack vendor either with ADK or shell.
ADK says cant find context for system/apps probabby its cant find selinux perms in file_contexts as its vendors its should not need that
And with Shell method can't say log are not getting create
Please looks and thanks for your work
Luffy.d said:
Can't repack vendor either with ADK or shell.
ADK says cant find context for system/apps probabby its cant find selinux perms in file_contexts as its vendors its should not need that
And with Shell method can't say log are not getting create
Please looks and thanks for your work
Click to expand...
Click to collapse
Vendor needs file_context especially plat_file_context it maybe missing something. I will look into it soon as currently I'm working on new project. So this might take a little while, but for sure I'll fix this.
[email protected] said:
Vendor needs file_context especially plat_file_context it maybe missing something. I will look into it soon as currently I'm working on new project. So this might take a little while, but for sure I'll fix this.
Click to expand...
Click to collapse
Thank you and no hurry
and here the exact error
error: build_directory_structure: cannot lookup security context for /system/app
Wow nice.
This can decompile framework-res.apk ans systemui.apk without errors anf uknown folders? Means java problem?
Good work, thank you.
Wysłane z mojego SM-G930F przy użyciu Tapatalka
Luffy.d said:
Thank you and no hurry
and here the exact error
error: build_directory_structure: cannot lookup security context for /system/app
Click to expand...
Click to collapse
I'll contact you once I will look up in this issue and fix it.
nalas said:
Wow nice.
This can decompile framework-res.apk ans systemui.apk without errors anf uknown folders? Means java problem?
Good work, thank you.
Wysłane z mojego SM-G930F przy użyciu Tapatalka
Click to expand...
Click to collapse
Yes it will unpack framework-res.apk and system ui. Just make sure when you want to decompile these system apps make sure to check the option 'import as dependencies' to not get any decompiling and compiling error further.
For Java problem I still get no response to issue with the latest Java problem. I think we still have to use lower Java version.
Android pie repacked system_ext.img can't boot.
Werewolf 99 said:
Android pie repacked system_ext.img can't boot.
Click to expand...
Click to collapse
Well I need some more info on this issue a logcat or something else. From your info I deduct following things like!
1. Your ROM might but using sparse image not ext if that's the case convert the image and then flash.(since sparse image omits some empty blocks)
2. I need to know the original image size and new compiled image size (if you have not made any changes then how much difference is present in their size).
Also let me know if you are flashing the new image using sp tool (for mtk devices).
futuretricks
thanks for this
Thanks for Your Share
EnerJon said:
Nice tool keep up the good work!
Sent from my Redmi 4X using Tapatalk
Click to expand...
Click to collapse
Thanks
cant use without a license, script download function is locked.. This must be under "paid software"not here.
guap said:
cant use without a license, script download function is locked.. This must be under "paid software"not here.
Click to expand...
Click to collapse
As discussed with the moderator this is part of ADK which is free to use even after trail period https://www.google.com/amp/s/forum....adk-android-reverse-engineering-t3803044/amp/
So if this is not working try original ADK which works after expiry date
I keep trying to download the script but the file is 0 kb and wont install. Any help?
Arden said:
I keep trying to download the script but the file is 0 kb and wont install. Any help?
Click to expand...
Click to collapse
Check your PM