Hello,
This post can't be said as a tutorial in itself, But is a tutorial shared by a fellow XDA Member. I tested it on our Desire X and I was able to get the init.d active on Stock JB. No need to modify the Kernel since we haven't got the Kernel Sources from HTC yet.
Init.d can be used to start scripts at android bootup.
Refer to this tutorial for enabling it on your device.
http://forum.xda-developers.com/showthread.php?t=1710980
Summarizing that Tutorial, This is what you have to do.
Step 1. Flash the attached ZIPS Easy_InitD_1.1.zip & Init_D_Test.zip from Recovery.
Step 2. Reboot the device.
Step 3. Open Root Browser and go to /data/ folder and check if there is a file named Test.Log.
If it exists then your Init.D is working, Also you will find the init.d folder in /system/etc/ folder.
Hope it helps.
Thanks to Smokin1337 for the original Tutorial.
And this works even with HTC write protection enabled?
EDIT: Didn't read carefully enough... It's flashed via recovery, so it has to work...
delete.
Related
I am trying to go back to stock ROM and use the Bares' Init.d Scripts Using Stock Kernel (V3).
I reflashed the stock GB ROM using flashtool, rooted and installed xrecovery 0.3. After that, I installed Bares' INIT-D-RUNNER-TWEAKS-V3.zip using xrecovery and rebooted. When ever I try to use wifi I get "Error" just below the toggle to turn it on and i does not work.
It seems like someone else had this problem, but Bares says tha wifi errors shouldn't happen, see:
http://forum.xda-developers.com/showthread.php?t=2174564&highlight=wifi
I tried reinstalling three times (install original ROM and after that apply the Init.d scripts) in an unlocked bootloader X10. I then relocked the boot loader and tried again and I still get wifi problems.
Anyone else having problems like this? Is there a work around?
Obs: I could not post in the original threas as I am a newbie here and I am not allowed to post in the development section.
pjssilva said:
I am trying to go back to stock ROM and use the Bares' Init.d Scripts Using Stock Kernel (V3).
I reflashed the stock GB ROM using flashtool, rooted and installed xrecovery 0.3. After that, I installed Bares' INIT-D-RUNNER-TWEAKS-V3.zip using xrecovery and rebooted. When ever I try to use wifi I get "Error" just below the toggle to turn it on and i does not work.
It seems like someone else had this problem, but Bares says tha wifi errors shouldn't happen, see:
http://forum.xda-developers.com/showthread.php?t=2174564&highlight=wifi
I tried reinstalling three times (install original ROM and after that apply the Init.d scripts) in an unlocked bootloader X10. I then relocked the boot loader and tried again and I still get wifi problems.
Anyone else having problems like this? Is there a work around?
Obs: I could not post in the original threas as I am a newbie here and I am not allowed to post in the development section.
Click to expand...
Click to collapse
Hi bro, we need to edit install-recovery.sh script inside zip to include wifi module, please refer to HERE.
So, please use this zip, just flash it through Xrecovery, then it should be fine.
FYI
Regards
It didn't work out
Bares said:
Hi bro, we need to edit install-recovery.sh script inside zip to include wifi module, please refer to HERE.
So, please use this zip, just flash it through Xrecovery, then it should be fine.
FYI
Regards
Click to expand...
Click to collapse
First, thanks Bares for ansewring fast. But I am sorry to say that I did not succeed. First, I tried to simply add the line
insmod /system/lib/modules/wifi.ko
in the middle of install-recovery.sh and it didn't work out. I thought the reason was that I did not add the wiki.ko file to /system/lib/modules in the generated zip and started to look for it. I found the following the stock wifi modules from here. I got the modules from the x10_gb_stock_wifi_modules.zip file and added them to my tweaked INIT.D zip but it didn't work out. Anything that I am missing?
pjssilva said:
First, thanks Bares for ansewring fast. But I am sorry to say that I did not succeed. First, I tried to simply add the line
insmod /system/lib/modules/wifi.ko
in the middle of install-recovery.sh and it didn't work out. I thought the reason was that I did not add the wiki.ko file to /system/lib/modules in the generated zip and started to look for it. I found the following the stock wifi modules from here. I got the modules from the x10_gb_stock_wifi_modules.zip file and added them to my tweaked INIT.D zip but it didn't work out. Anything that I am missing?
Click to expand...
Click to collapse
Hmmm..., this problem could be happened if the rom wasn't settled properly too.
So, please try these steps (exactly) :
- Revert back to stock and setup the phone.
- Root it with the latest Flashtool and choose SuperSU !!!
- Install Xrecovery and let the rom settled first !!!
- Check an everything including wifi !!!.
- If its all working good then flash my script (see the thread for the latest one) through xrecovery and dont get rush on the first 2~3 reboot.
- And check the result.
Regards
It still does not work
Bares said:
Hmmm..., this problem could be happened if the rom wasn't settled properly too.
So, please try these steps (exactly) :
- Revert back to stock and setup the phone.
- Root it with the latest Flashtool and choose SuperSU !!!
- Install Xrecovery and let the rom settled first !!!
- Check an everything including wifi !!!.
- If its all working good then flash my script (see the thread for the latest one) through xrecovery and dont get rush on the first 2~3 reboot.
- And check the result.
Regards
Click to expand...
Click to collapse
I tried as you suggested and it didn't work. I tried both with your V4 scripts and with my modified version to include the "insmod /system/lib/modules/wiki.ko". Both did not work after some time to settle the original ROM (with 3 reboots) and some time to settle the modified ROM (3 more reboots).
I have also tried your new STOCK-GB-MOD-RELOAD.zip update file, but it didn't work either.
One thing I noticed is that your original update files delete the wifi.ko module from the /system/lib/modules directory that exists in the stock ROM. I even copied wifi.ko to my computer and cried an small zip that can be flashed by xrecovery to restore that file, but it is not enough to get it working. I tried to read your INIT-D-RUNNER-TWEAKS-V4 to see what it was doing but I did not understand how it changes wifi (I could not even find out where wiki.ko wasw being deleted).
It is a really shame, as your new STOCK-GB-MOD-RELOAD.zip looks exactly as what I wanted.
Anything else I should try?
pjssilva said:
I tried as you suggested and it didn't work. I tried both with your V4 scripts and with my modified version to include the "insmod /system/lib/modules/wiki.ko". Both did not work after some time to settle the original ROM (with 3 reboots) and some time to settle the modified ROM (3 more reboots).
I have also tried your new STOCK-GB-MOD-RELOAD.zip update file, but it didn't work either.
One thing I noticed is that your original update files delete the wifi.ko module from the /system/lib/modules directory that exists in the stock ROM. I even copied wifi.ko to my computer and cried an small zip that can be flashed by xrecovery to restore that file, but it is not enough to get it working. I tried to read your INIT-D-RUNNER-TWEAKS-V4 to see what it was doing but I did not understand how it changes wifi (I could not even find out where wiki.ko wasw being deleted).
It is a really shame, as your new STOCK-GB-MOD-RELOAD.zip looks exactly as what I wanted.
Anything else I should try?
Click to expand...
Click to collapse
Hi bro,
The last options is by remove these 2 lines below from instal-recovery.sh script inside zip provided (STOCK-GB-MOD-RELOAD.zip) :
HTML:
#init.d runner
busybox run-parts /system/etc/init.d/
BUT, ... the problem is : you will lost init.d runner for Stock Kernel, and it cause all tweaks will not run for sure.
The result is the rom will feel a bit slower than it should be.
Note : To be honest, i'm little bit confusing here, because everything should be fine.
OR : Use custom kernel for Locked Bootloader ( Doomkernel V6 for Locked Bootloader).
OR :
Just simply unlock the bootloader (it's really safe, but you have to follow the proper procedure on this), the simply procedure is :
- Revert back to Stock Rom using PC Companion or SEUS or Flashtool (Download the latest Flashtool Version (see the thread about how to unlock for more detail info, read it carefully!!!)., and then unlock your bootloader using this Flashtool.
Note :
Don't assume if got doubt about this.
- Flash custom kernel using above Flashtool (DoomKernel V6 integrated Bootmanager V2 Auto Rooted by Championswimmer is my recommendation) , because it's using Original Sony's boot splash logo.
- Flash above zip (STOCK-GB-MOD-RELOAD.zip) through Xrecovery.
- Finally you have to flash wifi modul for above kernel (find it on DoomLord's Thread).
Hope this help
Regards
Intalling another kernel does not work...
Hi,
I had a version with a prestine Stock + STOCK-GB-MOD-RELOAD.zip[/B] through Xrecovery. And I installed championswimmer kernel on top of it (thinking it would restore wi-fi) and it didn't work. That is realluy strange. I am starting to fear that the problem is with my X10 (it has some odd behaviors, like it always become slow when using a Ferakernel).
I'll try your first suggestion (turn off init.d scripts) and let you know how it went here.
Anyhow, great thanks!
Improvement
pjssilva said:
Hi,
I had a version with a prestine Stock + STOCK-GB-MOD-RELOAD.zip[/B] through Xrecovery. And I installed championswimmer kernel on top of it (thinking it would restore wi-fi) and it didn't work. That is realluy strange. I am starting to fear that the problem is with my X10 (it has some odd behaviors, like it always become slow when using a Ferakernel).
I'll try your first suggestion (turn off init.d scripts) and let you know how it went here.
Anyhow, great thanks!
Click to expand...
Click to collapse
I tried to turn off init.d scripts and it didn't work!
It was getting into my nerves. So I decided to look inside your INIT-D-RUNNER-TWEAKS-V4.zip file to see if something was weird to me. I am an old Linux desktop user and it looked very strange a line in the update-script script inside META-INF/com/google/android:
delete_recursive SYSTEM:etc/init.d
This woudl delete the whole /etc/init.d directory, somthing that looks very dangerous from a desktop user. So I just commented it and created a new zip file (allowing the copy of your custom init.d scripts, just avoid the full deletion before hand). I was sure it would not work, but it did... Wifi is working after I install this new zip.
I plan now to take a close look at exactly what files are being deleted to find out what should remain in order to keep wifi working in my phone. I'll let you know when I get it right. Now I have to leave as real life is calling me!
I found a solution
I found the problem an the solution.
Just after installing the stock rom, rooting, and installing xrecovery, there is a single file in /system/etc/init.d. It is called 00modules (see attachment). It looks like it create symlinks from the currect kernel modules to /system/lib/modules. This file is essential to get wifi working in my X10.
Since Bare's mods, like STOCK-GB-MOD-RELOAD.zip, delete all the files in there I end up without wifi after installing them.
The solution is simple. Just add this file to STOCK-GB-MOD-RELOAD.zip in "system/etc/init.d". It will them be copied back after being erased. Wifi works and I get Bare's mod fully functional.
Thanks Bares fo your mod!
pjssilva said:
I found the problem an the solution.
Just after installing the stock rom, rooting, and installing xrecovery, there is a single file in /system/etc/init.d. It is called 00modules (see attachment). It looks like it create symlinks from the currect kernel modules to /system/lib/modules. This file is essential to get wifi working in my X10.
Since Bare's mods, like STOCK-GB-MOD-RELOAD.zip, delete all the files in there I end up without wifi after installing them.
The solution is simple. Just add this file to STOCK-GB-MOD-RELOAD.zip in "system/etc/init.d". It will them be copied back after being erased. Wifi works and I get Bare's mod fully functional.
Thanks Bares fo your mod!
Click to expand...
Click to collapse
Oooops, OMG i really really... forgot to include it, i though i was .
Really sorry, will update my script immediately, thanks you so much bro :good:.
Best Regards
[email protected]
---------- Post added at 07:49 AM ---------- Previous post was at 07:38 AM ----------
pjssilva said:
I tried to turn off init.d scripts and it didn't work!
It was getting into my nerves. So I decided to look inside your INIT-D-RUNNER-TWEAKS-V4.zip file to see if something was weird to me. I am an old Linux desktop user and it looked very strange a line in the update-script script inside META-INF/com/google/android:
delete_recursive SYSTEM:etc/init.d
This woudl delete the whole /etc/init.d directory, somthing that looks very dangerous from a desktop user. So I just commented it and created a new zip file (allowing the copy of your custom init.d scripts, just avoid the full deletion before hand). I was sure it would not work, but it did... Wifi is working after I install this new zip.
I plan now to take a close look at exactly what files are being deleted to find out what should remain in order to keep wifi working in my phone. I'll let you know when I get it right. Now I have to leave as real life is calling me!
Click to expand...
Click to collapse
I create this line below :
delete_recursive SYSTEM:etc/init.d
Just to make sure no additional tweaks on init.d (and this is for users that don't want to fresh install the rom) , so the rom will 100% run with my files, just is't.
BTW, thanks a lot for the finding bro :good:. I have update my script to the FINAL one (see my thread), and it seem will be no more update after this one.
FYI
Best Regards
Well i have locked bootloader and i wanted something new like a CM rom and i found this thread.
AOKP build 40 for locked bootloader LWW
The only problems is that the rom came with a fews bugs.
-Problem with Videos.
-And not be able to boot onto recovery.
I solve the second one, reading a few threads and testing and erros. I hope this could be usefull for someone other than me.
First of all thanks to script created for ATIS112 and the post of an0nym0us_ that helped to make CWM fully working without FC on rom.
The first step was copy from what Atis112 did for the aokp rom for locked bootloader on Xperia U separating the script for recovery and the ramdisk.
So how an0nym0us_ noticed, if we changed the first line of the recovery scripts.
from this
Code:
#!/system/xbin/sh
to this
Code:
#!/system/xbin/bash
and in the separated ram disk we maintain the first line without change it. Problem solved. We got fully working CWM recovery for this nice rom.
Here i upload my two script for faster use. Just push it to system/bin
Code:
[ATTACH]2038085._xfImport[/ATTACH]
[ATTACH]2038086._xfImport[/ATTACH]
P.S: I hope someone could help me with the video problem. Reading i found that the problems came with the build or maybe with the stock kernel. I don't know really. So enlighten me please.
darkbeowulf said:
Well i have locked bootloader and i wanted something new like a CM rom and i found this thread.
AOKP build 40 for locked bootloader LWW
The only problems is that the rom came with a fews bugs.
-Problem with Videos.
-And not be able to boot onto recovery.
I solve the second one, reading a few threads and testing and erros. I hope this could be usefull for someone other than me.
First of all thanks to script created for ATIS112 and the post of an0nym0us_ that helped to make CWM fully working without FC on rom.
The first step was copy from what Atis112 did for the aokp rom for locked bootloader on Xperia U separating the script for recovery and the ramdisk.
So how an0nym0us_ noticed, if we changed the first line of the recovery scripts.
from this
Code:
#!/system/xbin/sh
to this
Code:
#!/system/xbin/bash
and in the separated ram disk we maintain the first line without change it. Problem solved. We got fully working CWM recovery for this nice rom.
Here i upload my two script for faster use. Just push it to system/bin
Code:
[ATTACH]2038085[/ATTACH]
[ATTACH]2038086[/ATTACH]
P.S: I hope someone could help me with the video problem. Reading i found that the problems came with the build or maybe with the stock kernel. I don't know really. So enlighten me please.
Click to expand...
Click to collapse
No offence but the last couple of posts on that thread were exactly what you said. You should read before you post unnecessary things.
Sent from my WT19i using xda app-developers app
But it doesn't said exactly the same. They didn't tell you that you need to separate both scripts. The original script for recovery and ramdisk was only one.
But doesn't matter i had been testing CWM and it doesn't work. You could boot to recovery without problems, but apparently recovery work in another data folder different from ramdisk. I'm trying to fix this.
Finally i'm just trying to make something for people that wanted to use that rom. And with no offense you could try to really read the and at least comprehend the last posts of that thread. They only gave the solution for make recovery boot, but rom got a lot of FC and not work anymore. I make both, recovery and rom work.
Finally i fixed the problem with data folder.
Comparing some files from ROM recovery and 5.0.2.7 recovery files i noticed that the sh script in the folder xbin was corrupted or wrong in some way.
so i pushed the original sh files that comes with the 5.0.2.7 recovery (ROM version recovery --> not tried yet with version 5.5.0.4) to the following folder.
Code:
sytem/xbin
Now i changed back the first line of the chargemon script to the original.
Code:
#!/system/xbin/sh
The problem that i faced here was that the ramdisk used the same shell and for some reason it got a lot of FC with this, like before when we used bash for chargemon script. But with a little change in the ramdisk script i could bypass this and it worked. I tested a few zip with the recovery, changed bootanimation and adding some cameras and no problems.
So in the ramdisk script i changed the first line to this.
Code:
#!/system/bin/sh
Like before i leave all the files here.
Code:
[ATTACH]2040561._xfImport[/ATTACH]
This is not for flashing.
Instructions:
Push the files chargemon and ramdisk to system/bin (remove or replace older files if needed and set permission to rwxr-xr-x)
and the file sh to the folder system/xbin (remove or replace older file if needed and set permission to rwxrwxrwx)
And please if someone could link this post to the original thread. That way is easier for the rom users.
Dear Admins,
Could we get a forum setup for the Cube U27GT WiFi version? I dug around on the site a bit beforehand but didn't see one, I apologize if I missed it and please direct me there if I did.
I have this tablet and I am doing some initial basic firmware development for it and want a proper place to start putting threads.
Dear Dev Community,
I can't root this bloody thing... At least, not the rom itself. Let me explain...
I can flash the stock rom from Cube and that can be rooted using Kango Root. --Fine...
However, I can't figure out how to replicate this when I make my own rom.
Thus far, here is what I have attempted...
1. Setup dsixda's excellent kitchen on my Ubuntu workstation.
2. Unpack the rom, clean things up, manually put the boot image into the dsixda unpacked working rom folder, run dsixda's root functionality (which add SU binary to xbin and SuperSu apk file to app folder as well as do some things with the boot image file).
3. Rather than using repack with Dsixda (which makes an update.zip image which I can't use because the stock recovery environment on this device can't flash zip update files and I can't for the life of me figure out how to get and or make a working CWM or TWRP recovery image for this unit)...
4. What I do is I run commands in linux to unpack the stock rom to another directory and mount that directory, then clear out a bunch of folders and then manually copy in my files from dsixda's working folder, then repackage up my unpacked stock rom into a new system.img file.
5. Then copy my now modified boot image, system image, and also userdata image (I modify that as well as that is where most all of the chinese bloatware is loaded from) to my SP_Flash_Tool, generate new checksum.ini file and flash normally...
What I get as a result...
1. As long as I am really careful with how I copy files into my new image, the new system flashes okay (if I am not careful, after flash USB storage for some reason has a format error and the system will boot but can't mount USB storage and other odd issues ensue as a result).
2. Assuming everything flashes okay, and no issue with USB storage partition, I have SuperSU installed and when I go to use an app (ES File Explorer or Root Checker) that require's root, I do get the prompt. However none of the root functions actually work and Root Checker tells me I am not rooted.
That is as far as I have got. So as a result, I have a really nice, westernized, cleaned up rom but with no root.
Anyone have any ideas?
This is my first adventure into mod'ing MTK roms so I am sure I am doing all kinds of things wrong . I had a good bit of experience on Rockchip SoC's before this though.
Kind regards and thanks in advance!
Roman
Figured it out!
So I finally did the following rather hackish work-around...
1. Flash stock firmware...
2. Root with Kingo Root
3. Enabled ADB
4. Attach to PC and fire up MTK Droid Tools
5. Take a full backup
6. Modify the system image from the backup and make changes
7. Put that in new firmware flash package
8. Flash new firmware
YAY - Cleaned up rom, modified, with root!
Once I get it all packaged up and uploaded to mtkfirmware.com I will post a link for anyone that wants a cleaned up rom with root!
The only downfall of the above method is that it absolutely requires that the developer have a device on hand because you can't just root the stock image file (at least, I couldn't figure out how... - bleh...
Kind Regards,
Roman
Dear roman,
Thanks for your hard work.
I have a simple question (I think) and if you have the time to reply or -any other android guru- I would be thankful.
My later issue was with a U27GT cube tablet, but I have others, one for each kid, and this is more of general question.
I am reading this and other forums about how to flash tablets from PC. My question is:
Can the flashing process be done from a SD card?
Thanks a lot and regards,
Fernando
SKorea
Hi i just created this zip to install init.d on our phone (G530H)
For those who dont know what is the "init.d" its just a folder on the system where you can put some scripts and will run everytime you start the phone, its usefull to clean some cache, get better performance, zipalign etc. theres a lot of scripts on the web but i dont have time to test all of them so, heres a zip to install this folder, it includes the zipalign binary, tested and fully working, you can also google some scripts, test them and share the results with us
Flash it on cwm or twrp and enjoy
To run init.d scripts you need a custom kernel that support it or enable it on stock kernel. Without these changes , you will just have a new folder in your system...
Humberto.Ortega said:
To run init.d scripts you need a custom kernel that support it or enable it on stock kernel. Without these changes , you will just have a new folder in your system...
Click to expand...
Click to collapse
then... How do this worked?
Dam7lc said:
then... How do this worked?
Click to expand...
Click to collapse
I think this flashable zip has already enabled init.d support in stock kernel. I searched how to enable this support and I found we have to install the file "install-recovery.sh" in system/etc. I download your zip file and I saw that this file is present...
So this zip file doesn´t contains only script, but enable the init.d support for the stock kernel :highfive:
We can check this in /data/local/tmp...there should be a txt file there named "init.d_log_test.txt"
Sorry my mistake
I'll flash it and report later....
Thanks man!!
PLEASE MAKE ONE FOR G530P to enable gsm
To my speculations it seems the g530p is no different from the g530 variants p/h/t/t1 and the others as they all have the same qualcomm baseband but as the cdma feature is enable and the others are lock can you gather a team and make this possible to create a baseband or modem that edit these fields and enable gsm/umts or any other bands to work globally as well as the init.rd
thanks
how to port a rom for qualcom rom from almost same chipset?
THATS EASY
What Required?
1 laptot or computer
2. DEODEX TOOL
3. UNPACK/REPACK BOOT.IMG TOOL
4.NOTEPAD+
5.7Z OR WINRAR
6. meld compare tool (but no need if you have some xp)
5. A BRAIN
IF SO ENOUGH TO PORT A ROM
LET START
PORTING TW ROMS FOR ...
EG ; J5OOF(LL) FOR 530 GRAND PRIME
STEP 1
Boot.img edition
1. Unpack j5 boot.img nd 530f boot.img
2. REPLACE J5 dt_image nd kernel ( cause i use mkbootimg tool)
Then go ramdisk folder
3. COMPARE j5 default.prop with 530
add lines if missed
4. COMPARE init.carrier.rc
add lines if missed
that will fix multisim
5. Unpack J5 boot.img
IN THIS CASE
SOME TW ROMS NEED TO COMPARE fstb.qcom with your 530.
IF YOU NEED SWAP
EDIT fstab.qcom
add lines
/dev/block/zram0 none swap defaults zramsize=569547520
ENDED STEP 1
STEP2
build.prop edition
Change
ro.sf.lcd_density=320 to 240
then search oem props
if present delete this lines
END STEP 2
STEP 3
Replace files from 530 to port J5
in /system/etc/
replace folders
_ firmware
_blutooth
_wifi
Replace files
init***
IN /system/lib/
Replace files
modules/pronto/pronto_wlan.ko (wifi)
In /system/vendor/
replace folder
/lib/egl (auto rotate)
/egl/firmware
Replace&add files
first add your vendor /lib from your 530 without replacing any files or folder
Then replace from 530
libactuator***
libchromatix***
libmm***
libmmcamera2***
libmmcamera***
#CAM
END STEP3
STEP4
EDITING updater-script
search lines started with assert
if you found delete this lines
END STEP4
final step
archive ZIP
boot
system
META-INF
END
NOW ENOUGH TO BOOT UP.
FLASH VIA CUSTOM RECOVERY
I WILL WRITE BUG FIXING ND SOC PORTING GUIDE TOMORROW.
I SKIPPED DEODEX STEP ND SOME STEPs
I think that this thread will help you.
for second
Reserved
reserved
Wow great guide continue
Nice guide for new people. Now I think I can rest.
Nice guide @KoSett ?
Nice guide @KoSett ?
Nice :good:
Yes,Thanks
Hello @KoSett
Please try porting/fixing SM-G530T's Gwiz ROM for our SM-G530H.:good: @KoSett
What about miui?
I am busy for now , I will write complete guide for soc devices porting.
If so ,You can port for your device.
Wait it.
Can you make a guide to install g530h roms on g530t
Hi, I would like to know the names of the tools. 2. DEODEX TOOL
3. UNPACK / REPACK BOOT.IMG TOOL and links to downloads. If possible also some manual explaining the main files for mordification, knowing which file controls which function or set of functions to better understand and better edit since I am a beginner.
sorry for my english
DarkEvinho said:
Hi, I would like to know the names of the tools. 2. DEODEX TOOL
3. UNPACK / REPACK BOOT.IMG TOOL and links to downloads. If possible also some manual explaining the main files for mordification, knowing which file controls which function or set of functions to better understand and better edit since I am a beginner.
sorry for my english
Click to expand...
Click to collapse
http://www.mediafire.com/file/3z8xm03zdj9rr45/QURepack.zip
Boot unpack repack tool it is good
sorry for my english
Thanks for great guide bro...i,am trying to port Note 7 MM to Note3 N900 LP....is this guide working for that
PS:I will try to Port MM kernel From Galaxy tab s because it have the same Exynos 5400
Tnx
Thank you so much again
I ported G530W rom successfully..
But while trying to port Samsung A3 rom (5.0.2 with theme store) i got stuck on splash screen i dont know why?
Please help me?
And how to create updater-binary and updater-script..
(I used the j5 meta inf folder for G530W porting)
Thanks
For updater script, use Android kitchen. Or other tool.
Nd
You need to deodex successfully worked.
Some Deodex tool say success but it won't boot.It show boot again nd boot again.
I recommend to use android kitchen to deodex.
You can use format nd mount via your partitions.
Nd other way use Gwiz format ,mount, boot, codes in updaterScript.
Thankss