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....
Related
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?
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!
Ok folks, thanks to some leakage, some awesome users/testers, Chainfire and his root magic, and me with so of mine, you all have a fully functioning TWRP Recovery.
Official TWRP
Confirmed working on:
G900F
G900T
G900W8
G900I
G900P
G900M
Confirmed not working on:
G900H - exynos - Its recovery can found here
G900V - locked bootloader (thanks Verizon!!!)
G900A - locked bootloader (thanks AT&T!!)
Note: No one but yourself is responsible for what you do to your device.
People to Thank
TeamWin - for their awesome recovery.
TeamWin - for their hlte device repo I ported to the klte (kltexxx in this case)
ricky310711 - for providing dumps and testing
leoaudio13 - for providing access to device and testing
utkanos - for his original work on hlte (which all this is based off of)
Known Issues
Write permissions to internal storage.
How to install via adb shell
Have USB drivers installed
Connect phone to PC
Open terminal or cmd
Code:
adb push recovery.img /data/local/tmp/recovery.img
Code:
adb shell su -c dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
How to install with Odin
(USB) Disconnect your phone from your computer
Start Odin3-vX.X.exe
Click the PDA button, and select twrp-klte.tar
Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
(USB) Connect the phone to your computer
Make sure Repartition is NOT checked
Click the Start button
Wait for Android to boot
Done (if it took you more than 30 seconds, you goofed)
NOTE: Sometimes the device does *not* boot into recovery mode. Just do the entire procedure again if this happens. If it still will not install, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
The Goods
twrp-klte.tar - flash with ODIN.
recovery-twrp-klte.img - for manual flashing.
Official TWRP can be found here.
XDA:DevDB Information
TWRP for the Samsung Galaxy S5, Tool/Utility for the Samsung Galaxy S 5
Contributors
PlayfulGod, leoaudio13, utkanos, biggbiff
Version Information
Status: Stable
Stable Release Date: 2014-04-22
Created 2014-03-28
Last Updated 2014-06-08
Test imgs!!!!!!
Reserved
Yep the write permission is painful PG! but i accept to live with it for now )
Does this work on a SM-G900H?
0mega007 said:
Does this work on a SM-G900H?
Click to expand...
Click to collapse
Dunno until someone tries it.
PlayfulGod said:
Dunno until someone tries it.
Click to expand...
Click to collapse
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
{
"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"
}
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )
leoaudio13 said:
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )
Click to expand...
Click to collapse
umm I dont see that file in the system dump nor in cwm. So my guess is its a tibu issue.
not to mention, those look like app manifest permissions. And the Write permission overrides the read permission.
PlayfulGod said:
umm I dont see that file in the system dump nor in cwm. So my guess is its a tibu issue.
not to mention, those look like app manifest permissions.
Click to expand...
Click to collapse
Yup maybe. On the Nexus 5 Kitkat, TB made restored apps force closed. But TB team fixed it. But as far as i remember, When i was testing your recovery ( pretty sure it was cwm swipe) after 2 or 3 flashes, problem arose. Ricky and me thought it was an SD card issue ( wrong permission, full sd card or something like that ) but it turned out the problem was the platform.xml . Not so sure as if TB made any change to platform.xml or not.
leoaudio13 said:
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )
Click to expand...
Click to collapse
this was on a SM-G900H?
Did the recovery worked?
I just want it to completely wipe the phone before install new roms. so this bug doesnt matter to me if it worked
0mega007 said:
this was on a SM-G900H?
Did the recovery worked?
I just want it to completely wipe the phone before install new roms. so this bug doesnt matter to me if it worked
Click to expand...
Click to collapse
No its a F model. BTW, there is no Rom right now to install. ^^
according to a PM I just got, this doesnt work on G900H. By the description I was giving I think its the kernel and/or dtb. So I asked for a dump of the G900H stock recovery so I can extract the kernel & dtb from it.
PlayfulGod said:
according to a PM I just got, this doesnt work on G900H. By the description I was giving I think its the kernel and/or dtb. So I asked for a dump of the G900H stock recovery so I can extract the kernel & dtb from it.
Click to expand...
Click to collapse
Ok, thanks i hope you release H model recovery soon too
0mega007 said:
Ok, thanks i hope you release H model recovery soon too
Click to expand...
Click to collapse
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.
PlayfulGod said:
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.
Click to expand...
Click to collapse
Not yet, in about 2 weeks, but i wont order it until there is a root method available, and if it is from chainfire better
PlayfulGod said:
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.
Click to expand...
Click to collapse
Different chip maybe ? Pretty sure the one that test the H will be messed up cos there is no stock recovery atm
leoaudio13 said:
Different chip maybe ? Pretty sure the one that test the H will be messed up cos there is no stock recovery atm
Click to expand...
Click to collapse
From what I been told/seen its exynos. :\
PlayfulGod said:
From what I been told/seen its exynos. :\
Click to expand...
Click to collapse
I know its Exynos , but i guess the recovery will be different as well. Thats why i didnt dare to flash the root tool also gotta haave to wait. We can't dump recovery if there is no root ....
leoaudio13 said:
I know its Exynos , but i guess the recovery will be different as well. Thats why i didnt dare to flash the root tool also gotta haave to wait. We can't dump recovery if there is no root ....
Click to expand...
Click to collapse
yea it will be different. Ricky has a plan to try for root. And I'm just waiting for a recovery/boot dump lol
PlayfulGod said:
yea it will be different. Ricky has a plan to try for root. And I'm just waiting for a recovery/boot dump lol
Click to expand...
Click to collapse
Let see how it goes 2mo. I might ask for the H again hehe!:good:
Hi mate,
many thanks for the S5(G900F) TWRP recovery,
i have a question about the backup to extSD, it do not work
Error code:
E: Unable to create folder: /external_sd/TWRP/BACKUPS (error13)
E: Faild to make a backup folder
I have set this folder manuelly but the error comes again
Backup to internal SD works ok (big file with 3,4GB without set all Apps)
thanks in advance
Hi,
So although companies of course are bound by law to release kernel sources, and most of them do, there are sometimes circumstances where you still would like to see the disassembly of the kernel code. For example sometimes an ASM deadlisting can be easier to understand than complicated C++ code. Or maybe you suspect that your kernel code is slightly different than the source code your manufacturer supplied, maybe due to a slightly different configuration. It happens.
Anyway, whatever reason you might have, this is a small tutorial on how to obtain that kernel code in a deadlisting.
1) First of all you need of course to dump the boot image. I normally do this via: cat /dev/block/mmcblk0p17 > /sdcard/boot.img. But it depends on which partition the boot image resides. Use a partition tool to find out.
2) Seperate the kernel image from the boot image. I use Android Image kitchen myself.
3) The kernel image is self extracting. This means that it is just the compressed kernel + the decompression code to decompress it. We want to use a regular decompression utility so we want to strip that decompression code off in order for a normal decompression utility to handle it. Now, on older kernels (up to 2013 I think) you could use a tool like this to decompress the kernel: http://forum.xda-developers.com/showthread.php?t=901152 It's based on the fact that the kernel is Gzip compressed. However newer kernels use LZO compression. Luckily it's quite easy to do it manually. First of all you need to cut off the part upto where the kernel image starts (the decompression code). You need to search for 0x89 0x4c 0x5A 0x4F. That's 0x89 followed by "LZO", which is the start of the compressed file header. Now in my case I needed the 2nd hit (in my case the 1st hit is followed by some text and then like 0x50 bytes later follows the second hit, I needed that one). So cut off the part upto that, rename the file as a .LZO file and then you can just decompress it with any LZO decompresser, for example "Universal Extractor".
4) So now we have a decompressed kernel image. You could load this up into IDA pro already but reverse engineering will be hard since all symbols are missing. So how to get the symbols ? We can dump them from your phones memory too ! However the linux kernel is since quite some versions already protected against doing that, for obvious reasons. If you're root though, you can disable that protection via issueing:
Code:
echo 0 > /proc/sys/kernel/kptr_restrict
Next you can simply dump the symbols like:
Code:
cat /proc/kallsyms >/sdcard/symbols.txt
5) You now have a file containing all the symbols. But how to convert this into an IDA pro script ? You could write a simple tool or script that does it. Luckily I already did that for you, see the attached file However the symbol file you just dumped from memory wont contain the windows carriage returns after each line, which my tool needs (sorry too lazy to fix it up, lol), so you need to add them first. I use 'edit pad lite'. In that you simply copy en paste the file and save it. Once you open it in notepad you will now see it's perfectly carriage return formatted. Now use my tool to open it and it will create an IDC script
6) ready to load it all up in IDA pro now ! Open the kernel in IDA pro, select ARM as processor (that is if you're on such a phone of course) and load the kernel to the right address. Usually it will be the first address of your IDC script. But also a tool like Android Image Kitchen will show you the correct address. Then if the kernel is opened and loaded at the correct address, simply open the IDC script and it will add all symbols.
And there you have it ! A perfect deadlisting of your android kernel, containing all symbols ! Happy reverse engineering !
very nice one. good job bro.
Sent from my GT-I8190 using XDA Forums Pro
Subscribed, amazing thread and amazing tool, thank you for the insight, any more reversing knowledge with olly or ida is greatly appreciated.
Decent introduction, but this is just the beginning... Good for comparison purposes as you mentioned, but what else? *shrug*
Sent via Tapatalk on my Xperia Z
core7x said:
very nice one. good job bro.
Click to expand...
Click to collapse
berryman13 said:
Subscribed, amazing thread and amazing tool, thank you for the insight, any more reversing knowledge with olly or ida is greatly appreciated.
Click to expand...
Click to collapse
Glad you liked it guys.
CosmicDan said:
Decent introduction, but this is just the beginning... Good for comparison purposes as you mentioned, but what else? *shrug*
Click to expand...
Click to collapse
Not sure what you mean, you want me to teach you how to read ASM and/or use IDA pro ? That's a bit beyond the purpose of this thread I'm afraid.
@gekkehenkie11 Does the kernel decompressing end eventually ???
{
"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"
}
Im trying to follow your guide and im ok so far, i got the symbols from my phone, im decompresing the kernel right now.. we will see about using your script and IDA pro later.
THANK YOU!
Edit: i have the decompressed kernel now, i used the symbols to create the ida script using your script, now... i have to learn how to use it in ida
pirej said:
Edit: i have the decompressed kernel now, i used the symbols to create the ida script using your script, now... i have to learn how to use it in ida
Click to expand...
Click to collapse
Select ARM as processor and 0Xc0008000 as the kernel loading address (verify with your symbols, should be the same address as your first symbol) ! Good luck.
When i load the symbol-script made with your tool in to ida.. i get this type of error messages, a lot of them
C0103568: can't rename byte as 'vfp_propagate_nan' because the name is already used in the program.
C0F96E58: can't rename byte as 'byte_mux_ops' because the name has a reserved prefix.
C0F242FC: can't rename byte as 'ten_thousand' because this byte can't have a name (it is a tail byte).
Click to expand...
Click to collapse
There really is "vfp_propagate_nan" twice in my symbols dumped from my phone, is this normal or i did something wrong?
And I assume this would allow us to, like, recreate a particular kernel's source code when the original sources to it are unavailable, using extant code from a similar repo, right?
blakegriplingph said:
And I assume this would allow us to, like, recreate a particular kernel's source code when the original sources to it are unavailable, using extant code from a similar repo, right?
Click to expand...
Click to collapse
Hai I am new one n forum make any sample video understand
Post any video tutorials
After achieving deadlist how do we do to get kernel source in conventional format (like they have on github)..
I'm not asking u to write a guide. I'm asking "where i can find tutorial"
I find in 4pda forum to use "snowman decompiler" plugin in ida to convert deadlist to c++
Should i use it??
Hi I m looking for Lenovo K5 Note A7020 kernel.
Can anyone guide me to right direction.
Hi,
I m looking for Lenovo K5 Note A7020a48 kernel source can anyone guide me to right direction.
Hello, first thank you for this precious guide !
I'm currently facing problems reverse engineering kernel-ranchu kernel provided to modern AVD. Tried both of your methods and I can't get a valid kernel img. Any idea why ?
flaccidattempts said:
There is no certified way to reverse source code from binary. The process in which it has been compiled has to be reversed.
Now if you want to analyze binary and cross-examine it with android from source files, then you can derive using basic lamba functions to infer missing pieces.
But..... binaries can be engineered in a way that the code becomes obvious ESPECIALLY if you have Android from Source.
Essentially, you can download android from source using google repo tool, repo the release edition, compare side by side, file for file, what is different.
I Use these linux command s
From there i use a custom python file that 'line for line' searches for the strings, if they match, it logs the match.
once done with that, it sends it over to sublime text, which for some reason, on rare occasions resolves the binaries immediately, especially when paired with the matching strings file.
For files that are obviously encrypted, i wait till the end and brute force popular hashes, map out links, use lambda functions and use general deduction to solve to source.
If you want to learn how to analyze binaries with linux watch "malware analysis" videos on youtube
Click to expand...
Click to collapse
OEM/Manufukturer has an open source policy but some of them don't publish the kernel source code. I found the helpful answer to reverse kernel and I'll put it in the right suitable place.
lol im sorry. this is what im working with
unless you are trying to get from img to bin? or trying to get bin to text? or bin to c?
blu will not post there source or email me back, so im going to reverse engineer it to piss them off. Decompilers for llvm and clang and such exist. blueline hasnt put to much effort into hiding the source. I found a json @ link file that simplified the process
flaccidattempts said:
lol im sorry. this is what im working withView attachment 5622895
unless you are trying to get from img to bin? or trying to get bin to text? or bin to c?
Click to expand...
Click to collapse
IMG_Extractor_3.0.0.zip
drive.google.com
I extracted boot.img with img extractor v3.0.0 and get a compressed kernel image. I'm not sure what format it is but I want to reverse it
download ghidra from github. start importing files to assembly code
{
"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"
}
EagleRootTool - Xperia M2 Lollipop Root Tool
based on iovyroot & rootkitXperia
Hi all!
I'm very happy to announce you that, thanks to iovyroot, and with a lot of help from zxz0O0, we managed to get a new root binary working on the Sony Xperia M2, meaning we don't actually need to use Kingroot anymore to root LBL devices under Lollipop (18.6.A.0.182, and probably 18.6.A.0.175 too) :victory:
Requirements:
Stock kernel, from Sony's stock firmware 18.6.A.0.182, Linux version 3.4.0-gc82e70f based.
ADB enabled
Settings -> About phone -> Click 7 times on Android Build to unlock Developer options, and USB Debbuging
ADB drivers installed (you can pick them from Sony Mobile's website)
Material Terminal, from Yaroslav Shevchuk, if you want to do the root process right from your device.
You can get it on Google Play or APKmirror
Usage:
Download the tool
Extract the files
Execute the install.bat with a double click if you're on Windows, or simply do "sh install_mobile.sh" on Material Terminal (remember to use cd /path/to/where/you/placed/it to change to the folder were you extracted the files)
Wait until the process ends. Your device will reboot automatically
Download: Version 2016/05/31
Please, consider donating (or at least saying thanks!) to the people involved in the project if this tool was useful to you! zxz0O0, Cubeundcube, AleksJ & myself
Special thanks to:
- @zxz0O0 for iovyroot and his help
- @cubeundcube for his rootkitXperia scripts
- @AleksJ for providing copymodulecrc, ric_mod and testing
Enjoy! That kitty is a bad kitty!
XDA:DevDB Information
EagleRootTool (Root any Xperia M2 in 5.1.1, LBL & UBL), Tool/Utility for the Sony Xperia M2
Contributors
linuxct
Version Information
Status: Beta
Current Beta Version: 2016/05/31
Beta Release Date: 2016-05-31
Created 2016-06-02
Last Updated 2016-12-17
Frequently Asked Questions
- Can I use the install_mobile.sh installer on Linux for PC?
No.
- Can I use any other Terminal app?
No. Have a look at the install_mobile.sh file, and you'll realize why.
- Can I use this with an already rooted device (such as kingroot) to change the SU management app?
Not advisable. Format your system first using a FTF & Flashtools.
- Is RIC working / will I have RW access to System after rooting with this?
RIC is killed by default in every boot thanks to a init.d script, called 00stop_ric, so you'll have RW access to system always.
- Will you port this to other Xperia devices?
Yes, if they decide to collaborate and it's kernel's supported (aka vulnerable to CVE-2015-1805). We'd need the full kernel offsets of that particular device, so that we can look for the ones we actually need.
Reserved
Nice work fella, not tried it myself but beats using kingroot that's for sure. Unfortunately I may never get to try it out my M2 is getting replaced in a few weeks.
can i use for 4.4.4 (LOL) i just ask
NieeLz said:
can i use for 4.4.4 (LOL) i just ask
Click to expand...
Click to collapse
There's already a kk one linuxct made its on here somewhere.
Very useful and helpful, probably not only for M2.
All is fine here.
NieeLz said:
can i use for 4.4.4 (LOL) i just ask
Click to expand...
Click to collapse
Just as Adrian said, there's already a tool for that lmao
RootXperia Toolkit 2015/09/26 (Or how to Root 4.4.4 without downgrading)
I think it'll work on the t2u/c3 aswell.
aidy.lucas said:
I think it'll work on the t2u/c3 aswell.
Click to expand...
Click to collapse
As it is right now, it won't. I need the kernel offsets from those devices (T2u, C3, E4 users, I'm looking at you), which can be easily get in an already rooted device through catting /proc/kallsyms to a file using > /path/to/your/sd/kallsyms.txt, for example. (more info on getting the kallsyms here). Also, it'd be neat to have the /proc/version and the firmware version installed on the device.
Please remember, the kernel timestamp must say it was compiled before December 2015 to ensure the vulnerability is still there.
Once we got that, I can just add the offsets we need to the offsets.c database and recompile the iovyroot binary, and there shouldn't be any reason to touch the other scripts since they should work out of the box
linuxct said:
Just as Adrian said, there's already a tool for that lmao
RootXperia Toolkit 2015/09/26 (Or how to Root 4.4.4 without downgrading)
Click to expand...
Click to collapse
aidy.lucas said:
There's already a kk one linuxct made its on here somewhere.
Click to expand...
Click to collapse
hahahah i mean if i download this i have one tool can root kitkat and lollipop btw thanks for reply
why the script doesn't exist in init.d folder after using this?
DavidMKD said:
why the script doesn't exist in init.d folder after using this?
Click to expand...
Click to collapse
00stop_ric gets created, doesn't it?
Maybe I dropped the ball on something, can I get the full output of the script?
P.S. The init.d is in /system/etc/init.d, maybe you were looking for it somewhere else.
DavidMKD said:
why the script doesn't exist in init.d folder after using this?
Click to expand...
Click to collapse
When the tool finishes its execution, 00stop_ric and 99SuperSUDaemon can be found in the /system/etc/init.d directory.
linuxct said:
00stop_ric gets created, doesn't it?
Maybe I dropped the ball on something, can I get the full output of the script?
P.S. The init.d is in /system/etc/init.d, maybe you were looking for it somewhere else.
Click to expand...
Click to collapse
AleksJ said:
When the tool finishes its execution, 00stop_ric and 99SuperSUDaemon can be found in the /system/etc/init.d directory.
Click to expand...
Click to collapse
Yes, indeed that's the folder. The folder gets created, the wp_mod.ko gets copied but the script stops at execution of stopric.sh script and after trying to remount the system. The script stops at that point and no 00stop_ric.sh script get's created. All files get stuck in data/local/tmp/ folder and nothing is created after that. I will try to run the script from terminal but I'm pretty sure that the program can't write on system at this point i.e. operation is permitted
DavidMKD said:
Yes, indeed that's the folder. The folder gets created, the wp_mod.ko gets copied but the script stops at execution of stopric.sh script and after trying to remount the system. The script stops at that point and no 00stop_ric.sh script get's created. All files get stuck in data/local/tmp/ folder and nothing is created after that. I will try to run the script from terminal but I'm pretty sure that the program can't write on system at this point i.e. operation is permitted
Click to expand...
Click to collapse
This situation is extremely weird, and uncommon, I would say...
If the ric_mod.ko gets copied, by using dd, then it means the case was chosen correctly, so there's no reason for not creating the 00stop_ric, since it's just about echoing some lines to the file, change the owner, the permission, and that's it, as seen in the pic attached.
May I have your current environment (firmware version, etc)? Was the device previously rooted, and un-rooted to test the tool? Any info is appreciated.
linuxct said:
This situation is extremely weird, and uncommon, I would say...
If the ric_mod.ko gets copied, by using dd, then it means the case was chosen correctly, so there's no reason for not creating the 00stop_ric, since it's just about echoing some lines to the file, change the owner, the permission, and that's it, as seen in the pic attached.
May I have your current environment (firmware version, etc)? Was the device previously rooted, and un-rooted to test the tool? Any info is appreciated.
Click to expand...
Click to collapse
Well I've reflashed the phone since it had some display repairs and I've tried this method to disable the ric and get root and all I've got was the root only. The ric wasn't disabled and the script to disable the ric only by alex wasn't working at all since it had conflicts with this tool. The firmware version is 18.6.A.0.182. The old fashioned way by using kingroot then changing it to SuperSU and applying the disable ric script works without a problem. I will try to reconstruct the problem by giving you the outputs from the script as soon as I can
DavidMKD said:
Yes, indeed that's the folder. The folder gets created, the wp_mod.ko gets copied but the script stops at execution of stopric.sh script and after trying to remount the system. The script stops at that point and no 00stop_ric.sh script get's created. All files get stuck in data/local/tmp/ folder and nothing is created after that. I will try to run the script from terminal but I'm pretty sure that the program can't write on system at this point i.e. operation is permitted
Click to expand...
Click to collapse
Very strange results.
Tested again on clean installation (1281-1516-18.6.A.0.182).
EagleRootTool_20160531.zip
MD5: 2e59c4963e0e8824cb774726d3743513
File Size: 3947624 bytes
http://pastebin.com/hgRhqfbk
Guys can I use this with a PC? And Lollipop version? I have a D2403
tquin said:
Guys can I use this with a PC? And Lollipop version? I have a D2403
Click to expand...
Click to collapse
Yes, and yes. Answers for both of your questions were already answered (by the context) in the OP.