Some guys have problem using a JB or KitKat because though their Boot-loader is Unlocked, they can not Use the ROM after flashing. Because the Touchscreen will not respond after the new ROM Boots up. So, they are stuck with the ICS Stock that Sony gave. There is a Thread Touch does not work
I was one of these guys.
Well Guess what I got a solution.
So, I am going to write the procedure directly. But first, go and thank these two people...
1. erw1n for this post http://forum.xda-developers.com/showpost.php?p=46276864&postcount=81
2. bangladeshi for this thread. [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)
I Got the Idea from them.
Special Note: I'm not responsible if you brick or damage your phone.
The procedure goes as follows. I'm giving the detailed Instructions later.
Download the desired ROM
Extract Touch Screen Firmware and related files from Stock Official Sony FTF or any other source
Open ROM with 7-Zip or any other Zip Software and replace the Firmware Files with Stock ones.
Modify the hw_config.sh file in the ROM if necessary.
Close the ZIP
Flash the ZIP with CWM
Now Goes the Details-
Step One: I Did it with only [ROM] [UB] [Kitkat] [4.4.2] CyanogenMod 11.0 NIGHTLIES. So it's not tested on any other ROM. Theoretically It should work on any ROM. So, Cheers Download your ROM.
Step Two: If you dont want to do all these, then just download the zip file in the attachment and unzip it. for the official Sony firmware files
Else,
You will need FlashTool and Stock Official Sony ICS FTF and Notepad++ or any similar code/text editor and 7-zip for this. You will also need ext2explore (If you know what you are doing then you can also download the CWM flashable one ROM.)
First Open the FTF in 7-zip. Extract the System.sin file and put it in a folder lets say, "ICS_Stock". Now open FlashTool. Go to Sin editor.Browse for the sin file and click on Extract Data. Now after it finish, you will see four extra files in the ICS_Stock folder. with different extensions. one will be ext4. (something like "system_S1-SW-LIVE-3065-PID1-0002-S1-PARTITION.ext4")
Close FlashTool, Open ext2explore (as administrator). Go to file, Open Image, and select the ext4 you just extracted.
browse through the files,
Go to system/etc/firmware, right click on ttsp_fw.hex, save it.
Go to system/bin, right click on cyttsp_fwloader, save it.
Go to system/usr, right click on the folder idc, save it.
Close the ext2explore
Step Three: Now open the downloaded ROM with 7-Zip. Now Pay very careful attention
Go to system/etc/firmware, and delete ttsp_fw.hex if exists.
Go to system/bin, and delete cyttsp_fwloader if exists.
Go to system/usr, and delete folder named idc if exists.
Go to system/etc, and extract file named hw_config.sh after extract and save it in the same folder as other files, delete the file from the zip.
Now again
Go to system/etc/firmware, and drag and drop the ttsp_fw.hex file you just saved. (There will be a warning "Are you sure, you want to copy files into archive.... bla.. bla.. bla..." just say Yes)
Go to system/bin, and drag and drop the cyttsp_fwloader file you just saved.
Go to system/usr, and drag and drop the idc file you just saved.
Now comes the vital Part,
Open the hw_config.sh file with Notepad++ you will find some lines like this one,
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex
# Audio jack configuration
if it is just like my example then, change the lines to
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex -force
# Audio jack configuration
(Just add a -force)
If its not like the example and you don't have a clue what to do, Ask in this thread, If I'm there, I'll reply what to change.
it could be something like below, (taken from the Chienise Guy ROM 6.2.A.1.100 Xiangxin X3
Code:
# Touch FW loader
dev=/sys/bus/spi/devices/spi9.0
fw=ttsp_fw.hex
app_id=`cat $dev/appid`
case `cat /data/ttsp_fw_update` in
"in_progress") flags=-force ;;
*) flags="" ;;
esac
case "$app_id" in
"0x3030") flags=-force ;;
*) echo $app_id > /data/ttsp_appid ;;
esac
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev $dev -fw /system/etc/firmware/$fw $flags
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
Here you may or may not change. but if you really want to change, change it to,
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex -force
# Audio jack configuration
Then save and close the hw_confif.sh file.
Now again go to your ROM opened with 7-zip, and Go to system/etc, and drag and drop the hw_confif.sh file you just saved.
Close the ROM Zip.
Step Four: your Fixed ROM is ready. Take all the Backups you need and don't need . Go to CWM, and also take all the NANDROID backup.
Now keep your fingers crossed and flash the Modified ROM as the instructions say in the Main Thread from where you downloaded the ROM.
If this solution works, Thank the ROM Builder first and then me.
Please Note: Do not distribute the Modified ROM without the permission of the Original Developer.
and Don't Blame Me or the Developer if the solution don't work for you. It worked for me.
If it worked for you, then Please tell us, for which ROM the solution worked. We can make a list of Compatible ROMs for this Modifications.
Up to now, this trick is confirmed to work on Two ROMS.
[ROM] [UB] [Kitkat] [4.4.2] CyanogenMod 11.0 NIGHTLIES
JB Thunder Strike
im really2 thank you.. for your tips..
yeah ,, now my xu rom JB Thunder Strike..!!
touchscreen problem solved..
erw1n said:
im really2 thank you.. for your tips..
yeah ,, now my xu rom JB Thunder Strike..!!
touchscreen problem solved..
Click to expand...
Click to collapse
The KitKat Nightly Is very stable and fast for me. Sometimes the Touch hangs again. I just remove the battery and re-insert it again. And Viola. it Works.
Glad that it worked. Now what I am going to work on is, how to make, Recovery Mode Touch work. I know it's tough, but possible.
CWM Flashable ZIP for recovery touch
I had noticed that, though the ROM Touchscreen works, but in recovery, the touch don't work. So, have made a CWM Flashable ZIP file, if you flash it, hopefully the touch will start to work inside the Recovery. Please note, This is not a permanent solution. You have to flash this file each time you go in recovery.
Once again, I tasted it with only CM11 Nightlies.
If it works, I will try to modify this file to act like a patch for all ROMs. So that, you can flash any ROM and after that you can flash this patch to make touch usable.
@[B]jatinrungta[/B] Can you test it for me?
I tried to extract from system.sin but I only got system.partinfo and system.yaffs2 files. I am trying to fix my mini pro (mango) touch screen and I used the stock ROM SK17i_4.1.B.0.431_(1249-7380).ftf to get the system.sin. Any thoughts?
edit:
Can you also provide an updated CM11 that has a fix on it for sk17i (mango)? I will really appreciate it.
evilfox7 said:
I tried to extract from system.sin but I only got system.partinfo and system.yaffs2 files. I am trying to fix my mini pro (mango) touch screen and I used the stock ROM SK17i_4.1.B.0.431_(1249-7380).ftf to get the system.sin. Any thoughts?
edit:
Can you also provide an updated CM11 that has a fix on it for sk17i (mango)? I will really appreciate it.
Click to expand...
Click to collapse
Sorry for the late answer.
But problem is, I don't have SK17i the set in my hand. So, I am not sure, the fix, I did, will work on your one.
Still, I'm going to download and make a cwm installable zip from the Sony stock ftf. I'm gonna download the FTF tomorrow, i have transfer cap and provide you a CWM file for CM11. Need to search the sk17i (mango) forums. But, you can try with a yaffs2 explorer, it'll work as ext2explorer.
pollob666 said:
Sorry for the late answer.
But problem is, I don't have SK17i the set in my hand. So, I am not sure, the fix, I did, will work on your one.
Still, I'm going to download and make a cwm installable zip from the Sony stock ftf. I'm gonna download the FTF tomorrow, i have transfer cap and provide you a CWM file for CM11. Need to search the sk17i (mango) forums. But, you can try with a yaffs2 explorer, it'll work as ext2explorer.
Click to expand...
Click to collapse
I will look forward for it. Anyway, I will try to use the yaffs2 and hopefully it has the same structure with your original post.
i have this trouble but is was like this when i flash GB back (i was on ICS stock rom)
But i try to revert and back to ICS and dont work
Can anyone help me please!
Xperia sola unresponsive touchscreen
Hi,
I tried the steps that you have suggested, But in the final part(hw_config.sh) with the code, i had something different. I dont know how to alter it. Can you help me out??
The code is below.
# Touch FW loader
dev=/sys/bus/spi/devices/spi9.0
app_id=`cat $dev/appid`
case `cat /data/ttsp_fw_update` in
"in_progress") flags=-force ;;
*) flags=-no-downgrade ;;
esac
case "$app_id" in
"0x3030")
flags=-force
;;
esac
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev $dev -fw /system/etc/firmware/ttsp_fw.hex $flags
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
bhatadarsh said:
Hi,
I tried the steps that you have suggested, But in the final part(hw_config.sh) with the code, i had something different. I dont know how to alter it. Can you help me out??
Click to expand...
Click to collapse
Yes, Just replace the lines with these below,
Code:
# Touch FW loader
#dev=/sys/bus/spi/devices/spi9.0
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /system/etc/firmware/ttsp_fw.hex -force
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
Go to system/usr, right click on the folder idc, save it.
Go to system/usr, right click on the folder idc, save it.
There is no IDC folder .....help me....
Related
IMPORTANT NOTE: Because people do not have respect for the work of other people or to the point of thanking all the links to the alternatives are "down" until further notice. Over 200 downloads and not a thank you?!
Thanks.
After receiving several PM `s trying to get my help in the installation of Froyo ROM` s i decided to create this little "How to" for the avoidance of doubt.
This is a guide based on the Windows XP System.
This guide is ONLY for Xperia X10.
This guide was based on information gathered and based on my own experience and presents, in my opinion, the best way to get what you want. Whenever possible I will present alternatives.
This guide has a starting point of the original ROM SE (no root) if you already have root access please go to step 2.
---------------------------------------
---------------------------------------
What you`ll need before proceeding:
- Download SDK from google (need help for this? go HERE)
- Make sure you`ve just one partition on your sdcard and on FAT32. More info HERE
- Before each and every step make sure you have USB Debugging checked (settings>applications>Development)
---------------------------------------
---------------------------------------
I WILL NOT BE RESPONSIBLE IF ANYTHING GOES WRONG
1. Getting Root Access
1st mode
- Download file rootme.tar.bz2 HERE and follow the instructions or use as an alternative SuperOneClickv1.5.5-ShortFuse;
- Reboot.
2nd mode
You can alternatively use THIS pre-rooted and with xRecovery allready instaled rom. Saying this, if you choose to install this rom can proceed to step 3
Use THIS tool if you have any trouble with Bin4ry one.
Bin4ry realease a new tool you can try it HERE.
2. Installing xRecovery
1st mode
- Download xRecovery HERE and do the installation by following the instructions.
2nd mode
For the case of having problems installing the xRecovery do the following:
- Download THIS version of xRecovery;
- unzip it and copy the content (3 files) to the root of your sdcard;
- Open cmd prompt (start>run and type cmd) - From now on i will call this adb shell. I also recomend that you create a shortcut to this on your desktop, since you will use this many times;
- Now go to tools folder where you install your SDK. In my case (C:\Program Files\Android\android-sdk-windows\tools>);
Now type:
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/busybox of=/system/bin/busybox
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/xrecovery.tar of=/system/bin/xrecovery.tar
reboot
Check your screen and give permition
- Reboot
- Press several times after "sonyericsson" appear on back button to confirm if xRecovery it`s installed. If it`s corrected installed you wil see your screen as the images bellow.
Although this guide is described for the installation of zhizu rom`s the process is exactly identical to the TripNRaVeRs and jerpelea rom`s
3. Installing Rom`s
This guide is for every rom that supports xRecovery process. I will not answer questions from other method.
- Choose the rom you want.
ZHIZU / TripNRaVers v2.1 / TripNRaVers vMIUI / jerpelea
3.1.
zhizu rom:
- Download-FreeX10 beta1.zip;
- Download gapps_latest_FreeX10.zip;
- Download FreeX10-beta1-hotfix4a.zip (at this point this is the last version, if a newer version exist please download that one. The process is identical);
- Create a folder at the root of the sdcard named ROMS;
- Create a folder inside ROMS called zhizu, TripNRaVers or jerpelea (dependind witch rom you`ll use);
- Copy the downloaded files to that folder;
- Reboot;
- Enter on xRecovery and:
3.1.1.
- Install custom zip;
- Choose custom zip from sdcard;
- ROMS (folder you created earlier);
- zhizu;
- Run the FreeX10-beta1.zip;
- Run the FreeX10-beta1-hotfix4a.zip;
- Reboot;
---------------------------------------
---------------------------------------
NOTES:
After that, probably you won`t have network and screen is crazy... do this:
Open adb shel again and type:
HTML:
adb shell
killall servicemanager
Your phone will reboot.
HAVE REAL ISSUES REGARDING "killall: not found"? type this instead (thks to NeoInc):
HTML:
adb shell
busybox killall servicemanager
If you`ve installed the TripNRaVers rom and if you have issues with wireless run this command on adb shell (thks to rodak ):
HTML:
adb shell
setprop net.dns1 192.168.1.1
If you having problems with su permission type (thks to AzureNightwalker ):
HTML:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
chmod 4755 /system/bin/su
---------------------------------------
---------------------------------------
(back on topic)
- After reboot enter on xRecovery again and go where you put your files again but this time you will run the gapps_latest_FreeX10.zip
- DONNE
If after instaling gapps_latest_FreeX10.zip you still don`t have google apps, please install THIS and then gapps_latest_FreeX10.zip
4.
If you want to install new market, please do this:
- Enter AT LEAST once in the old one;
- Copy THIS to the folder you`ve created earlier and run it from xRecovery.
---------------------------------------
---------------------------------------
CREDITS:
None of this would have been possible without the incredible work of our devs.
All the credit should be directed to them. Not for me. Just tried with this guide to help young (or not) to get phones rooted, install xRecovery and for installation of these incredible ROM `s.
Thanks to (in alphabetical order): (sorry if i forgot someone)
Bin4ry;
CLShortFuse;
jerpelea;
MarylandCookie;
rodak
th4r;
TripNRaVeRs;
XperiaX10iUser;
ZHIZU;
and all XDA users
|tips & tweaks|
some commands that you may require at some point
Copy to/from sdcard
HTML:
adb push /mnt/sdcard/<filename> - to copy the file to SD
adb pull /mnt/sdcard/<filename> - to copy the file from SD
Fix Facebook Sync (at the present TripNRaVeRs Rom may need it)
Please make back up first
Install to your Android using push command
HTML:
adb push ContactsProvider.apk /system/app/ContactsProvider.apk
adb reboot
Download ContactsProvider from HERE (thks XperiaX10iUser )
This will fix the Facebook sync, you might need to remove and add the Facebook account again.
If you loose root access for some reason, please open ADB shell and issue this command:
HTML:
chmod 4755 /system/bin/su
--------------------------------------------
--------------------------------------------
some tips & tweaks to play with
Let`s play with build.prop shall we?
CAUTION WITH THIS!!! ALL CHANGES MUST BE DONNE AT THE END OF THE DOCUMENT!!!
What will you get with this...
Well. In my opinion and only that, i think this way i can preform a much stable version of 2.2 Froyo released by zhizu.
After all apps installed (more or less 35) i get a very stable and fast rom (more or less 1500 on quadrant) and rarely had a FC.
So...like i said...that`s my 2cents.
1st mode - root explorer
You can make changes directly through RE by going on \system and then:
- Press and hold on build.prop file;
- Check all Permitions on the drop down menu;
- Press and hold on build.prop file (again);
- Choose open in text editor;
- After changes were made save and exit;
- Reboot.
2nd mode - Through Text Editor
To edit this one you must do this on a UNIX system base. You can use THIS to do that.
- Copy your build.prop to your sdcard and then to your pc;
- Open build.prop through NOTEPAD++;
- Now check all permitions for build.prop in \system folder
- After you made the changes proceed in reverse way and check all permitions again;
- Reboot.
This is your build.prop of your phone. Here we can do some tweaks in it.
Look carefully some already exist somo you have to add.
ro.sf.lcd_density=XXX (here you can put any value between 180/240) - This will affect the way you see your screen;
wifi.supplicant_scan_interval=XXX - This is how often your phone search for wi-fi spots and obviously will afect your battery life. Choose whatever you want in seconds. For instance, i have 360. Witch means my phone will search for wi-fi every 360 seconds.
dalvik.vm.heapsize=XXX (here you can put any value between 12/40) - This is how Android lead with apps. Lower value faster phone but big apps will crash. Higher value slower phone on small apps but faster on big ones). I have this to 40.
windowsmgr.max_events_per_sec=XXX (here you can put any value between 30/300) - This affect screen responseness of screen. You may try this if you have any problems with lag. I have this to 200.
mot.proximity.delay=XXX (here you can put any value between 0/300) - This will affect the time your screen goes off when receive a call. I have this to 150.
--------------------------------------------
--------------------------------------------
| Rom`s | Themes |
THIS ONLY WORK AFTER RIGHT INSTALATION OF THE ABOVE ROM´s
What is the joke of having rooted phone if we do not install anything to envy to our friends. Right?!
SEMPITERNAL THEME
XperiaX10iUser
wesvista
Whats wrong with my guide?
http://forum.xda-developers.com/showthread.php?t=908791
rodak said:
Whats wrong with my guide?
http://forum.xda-developers.com/showthread.php?t=908791
Click to expand...
Click to collapse
nothings wrong with it. if you read it goes further. root/xrecovery/rom`s and since so many people has sent me pm`s to explain them...
don`t get offensive
rendeiro2005 said:
nothings wrong with it. if you read it goes further. root/xrecovery/rom`s and since so many people has sent me pm`s to explain them...
don`t get offensive
Click to expand...
Click to collapse
From my guide:
"Feel free to help me improve this guide, just post here and I will update this post with all good tips!"
But hey, let´s have a lot of guides spread all around this forum just to get some credit
Hmm. Sorry. Got a question here.
Step 1 and 1a, is it the same? Or i need to do step 1 and then do step 1a?
And partition on my sdcard is already on Fat32, do I need to reformat it again to Fat32?
wanmeow said:
Hmm. Sorry. Got a question here.
Step 1 and 1a, is it the same? Or i need to do step 1 and then do step 1a?
And partition on my sdcard is already on Fat32, do I need to reformat it again to Fat32?
Click to expand...
Click to collapse
Hi,
1st. Like i said "alternatively". 1 is one way and 1a is another way. The diference between the two is the fisrt one you have to root after install and the second one came pre-rooted.
2nd. Since you`ve sdcard on FAT32 don`t have to do it again. Just be sure there`s ONLY ONE partition.
Hope it helps
Oh. sorry. I miss the "alternatively".
Which one is the best? 1 or 1a?
wanmeow said:
Oh. sorry. I miss the "alternatively".
Which one is the best? 1 or 1a?
Click to expand...
Click to collapse
depends on what you want. root or not rooted.
for the installation of above Rom `s you need to have root access.
Oh, ok. Thank you. I go download the files and try it first.
wanmeow said:
Oh, ok. Thank you. I go download the files and try it first.
Click to expand...
Click to collapse
you`re wellcome
tell me how it goes
nice guide.
tnx
Tehouster said:
nice guide.
tnx
Click to expand...
Click to collapse
wellcome
no need to thk me just click thks
Im stuck at SE white logo. If im not pressing back button, it will boot normally. Im thinking like giving up. >.<
wanmeow said:
Im stuck at SE white logo. If im not pressing back button, it will boot normally. Im thinking like giving up. >.<
Click to expand...
Click to collapse
Wicth process you follow?
From stock ir zhizu rom?
If you start from stock witch process you usr to install xrecovery?
As you know i've two possibilities on eatch one if you dont tell all things youve donne i cant help you
sent from my ****up X10 running amazing zhizu rom
Tool Aces Present..
FTF 2 Zip
Disclaimer:
Code:
[COLOR="Magenta"]@[/COLOR][COLOR="Blue"]echo off[/COLOR]
[COLOR="MediumTurquoise"]title[/COLOR] Disclaimer
[COLOR="Blue"]echo[/COLOR].
[COLOR="blue"]echo[/COLOR] I'm not responsible for any kind of damage that happens to you or your device. You are choosing doing this on your own and if incase anything goes wrong I will try to help you :)
[COLOR="blue"]echo[/COLOR].
[COLOR="blue"]exit[/COLOR]
About the tool:
This tool converts your FTF to a flashable rooted ROM in a few simple steps. Simple batch scripting has been used to make this.
How to use?(Will add screenshots soon)
1. Download and extract the f2z.zip
2. Now place your ftf in ftf folder
3. Now click RunMe.bat and press enter and let the tool do it's work.
4. Now select a compression size b/w 2048, 4096 and 8192 and press ENTER. I recommend using 4096 for ICS and 2048 for
GB.
5. Now the tool will do some final work. Do all the changes you want in your ROM by going to /system folder when prompted to do so.
6. Now press ENTER and the 7z window will open and compress your ROM. After it's done find your rooted, flashable ROM in rom folder.
Downloads:
Download from here.
Credits:
# abcdjdj for confirming it to work with ICS
Click to expand...
Click to collapse
XDA:DevDB Information
FTF-2-Zip, a Tool/Utility for the Sony Ericsson Xperia Mini, Mini Pro, Active
Contributors
Abhinav2
Version Information
Status: Stable
Created 2013-09-28
Last Updated 2013-12-11
good work.
trying it now
i got first comment. yay
Edit: Works perfectly. - ics
Doesn't work on "st15a" GB 4.0.2.A.0.62 .ftf file
Hello,
Thanks for the tool, however it doesn't work with "st15a" GB 4.0.2.A.0.62 .ftf...I have tried multiple compression values without success...it tries and sets up several empty directories, but there is an error that occurs and it goes to the next screen too quick for me to see the error.
This "st15a" .ftf is viable however with these "a" model firmwares there have been many incompatible programs (I am not sure why) and the "i" versions work without a hitch. Case in point...the readily available "One Click Root" works perfectly with "i" version models but the "a" versions do not work no matter how many times that are tried.
I am running Windows XP SP3.
Thanks so much for your effort though...I have been wanting to get this firmware rooted as a backup for my st15a and nothing seems to work.
Thanks again.
Do you know the steps to do it mannually? If yes pm me or aj the steps and any one will check whether the tool does that or not.
About the error try printscreening it
Regards
N
vjgrace said:
Hello,
Thanks for the tool, however it doesn't work with "st15a" GB 4.0.2.A.0.62 .ftf...I have tried multiple compression values without success...it tries and sets up several empty directories, but there is an error that occurs and it goes to the next screen too quick for me to see the error.
This "st15a" .ftf is viable however with these "a" model firmwares there have been many incompatible programs (I am not sure why) and the "i" versions work without a hitch. Case in point...the readily available "One Click Root" works perfectly with "i" version models but the "a" versions do not work no matter how many times that are tried.
I am running Windows XP SP3.
Thanks so much for your effort though...I have been wanting to get this firmware rooted as a backup for my st15a and nothing seems to work.
Thanks again.
Click to expand...
Click to collapse
OK then do the following-
0. Download the latest flashtool.
1. Extract your ftf to obtain system.sin with 7z or winrar.
2. Now go to flashtool and goto tools->SIN editor and browse for your system.sin. Then click dump data.
3. Now you will get a file named system.yaffs2. Now click on tools->extractors and select yaffs2. Browse for system.yaffs2 and extract it.
4. Now you will get a folder named system with your files in it. Then download my tool.
5. Goto imp folder and copy the META-INF folder and place it along(not inside) the system folder.
6. Now from the imp folder copy su binaries and paste it in the bin folder of the system folder you extracted.
7. Now copy superuser.apk from imp folder and paste it in apps folder of the system folder.
8. Now copy the busybox binaries from imp folder and paste it to xbin folder of the system folder you extracted.
9. Lastly select system folder and META-INF folder and zip the ROM via winRAR or 7z and done.
10. Enjoy
Thanks...I will give it a try and report back later.
Abhinav2 said:
OK then do the following-
0. Download the latest flashtool.
1. Extract your ftf to obtain system.sin with 7z or winrar.
2. Now go to flashtool and goto tools->SIN editor and browse for your system.sin. Then click dump data.
3. Now you will get a file named system.yaffs2. Now click on tools->extractors and select yaffs2. Browse for system.yaffs2 and extract it.
4. Now you will get a folder named system with your files in it. Then download my tool.
5. Goto imp folder and copy the META-INF folder and place it along(not inside) the system folder.
6. Now from the imp folder copy su binaries and paste it in the bin folder of the system folder you extracted.
7. Now copy superuser.apk from imp folder and paste it in apps folder of the system folder.
8. Now copy the busybox binaries from imp folder and paste it to xbin folder of the system folder you extracted.
9. Lastly select system folder and META-INF folder and zip the ROM via winRAR or 7z and done.
10. Enjoy
Click to expand...
Click to collapse
@ mnishamk
Thanks for your reply As far as the printscreen, it goes to fast to even do a printscreen, but thanks anyway
@ Abhinav2
I tried all the steps to the letter and am getting an error7...here is the actual error:
setting permissions...
set_perm: some changes failed
E:Error in /sdcard/402A062stock.zip
(status 7)
Installation aborted
Click to expand...
Click to collapse
It seems with the "st15a" 4.0.2.A.0.62 firmware, any modification of the stock, this error occurs. It is these "a" models which make it difficult to modify the firmware.
Any ideas?
Thanks so much for your time and help thus far...I had hopes when I saw your reply, but no go.
Thank u..!!
While installing the rom i get error while "Setting Permissions".. Installation gets aborted.
Do i have to modify the updater-script..??
Don't worry I'll update the updater-script in sm time. Sorry guys.
Cheers,
AJ
alokbina is now Abhinav2
Updated the tool. Now the updater-script won't give the error Enjoy :good:
Cheers,
AJ
Was great
updater-script to android 2.x.x
Do not you think it's better to add to updater-script for android 4
Code:
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
symlink("/system/fonts/Roboto-Regular.ttf","/system/fonts/DroidSans.ttf");
symlink("/system/fonts/Roboto-Bold.ttf","/system/fonts/DroidSans-Bold.ttf");
symlink("/factory/hdcp.keys","/system/vendor/firmware/hdcp.keys");
symlink("/data/etc/wifi/wl1271-nvs.bin","/system/etc/firmware/ti-connectivity/wl1271-nvs.bin");
Used by myself.
Also included in this
The possibility of adding language Persian
it doesn't work
its gave me 120 kp rom
@Abhinav2 would it work for xperia sola firmware??
Thanks & Regards
huss5221 said:
@Abhinav2 would it work for xperia sola firmware??
Thanks & Regards
Click to expand...
Click to collapse
Why don't you try and tell me
Cheers,
AJ
it's workin with manual way,, it shows 'installation aborted' at cwm, i continue anyway and stuck at bootanimation, i pull out the batery back to cwm clearing data n dalvik cache and it works but i can't charge my phone, i plug the device it shows nothing not even the blinking led and the rom is not rooted.
any idea?
azzazelium said:
it's workin with manual way,, it shows 'installation aborted' at cwm, i continue anyway and stuck at bootanimation, i pull out the batery back to cwm clearing data n dalvik cache and it works but i can't charge my phone, i plug the device it shows nothing not even the blinking led and the rom is not rooted.
any idea?
Click to expand...
Click to collapse
At what part did it show installation aborted? It might show some status error. Also which firmware? Give log.
Cheers,
AJ
Abhinav2 said:
At what part did it show installation aborted? It might show some status error. Also which firmware? Give log.
Cheers,
AJ
Click to expand...
Click to collapse
im sory i didn't save the log. All i remember its on cwm when setting the permission. status error 7. it is stock wt19i .587. and yes its still booting anyway but my rom cannot charging and not rooted
Abhinav2 said:
At what part did it show installation aborted? It might show some status error. Also which firmware? Give log.
Cheers,
AJ
Click to expand...
Click to collapse
Thanks for this awesome tool ...:thumbup:
But I want the link of the guide to CONVERT FTF TO FLASHSBLE ZIP without using this TOOL ...
Thanks
Rahil ... Jai Hind
Sent from my Xperia Live with Walkman using XDA Premium 4 mobile app
Abhinav2 said:
Tool Aces Present..
FTF 2 Zip
Disclaimer:
Code:
[COLOR="Magenta"]@[/COLOR][COLOR="Blue"]echo off[/COLOR]
[COLOR="MediumTurquoise"]title[/COLOR] Disclaimer
[COLOR="Blue"]echo[/COLOR].
[COLOR="blue"]echo[/COLOR] I'm not responsible for any kind of damage that happens to you or your device. You are choosing doing this on your own and if incase anything goes wrong I will try to help you :)
[COLOR="blue"]echo[/COLOR].
[COLOR="blue"]exit[/COLOR]
About the tool:
This tool converts your FTF to a flashable rooted ROM in a few simple steps. Simple batch scripting has been used to make this.
How to use?(Will add screenshots soon)
1. Download and extract the f2z.zip
2. Now place your ftf in ftf folder
3. Now click RunMe.bat and press enter and let the tool do it's work.
4. Now select a compression size b/w 2048, 4096 and 8192 and press ENTER. I recommend using 4096 for ICS and 2048 for
GB.
5. Now the tool will do some final work. Do all the changes you want in your ROM by going to /system folder when prompted to do so.
6. Now press ENTER and the 7z window will open and compress your ROM. After it's done find your rooted, flashable ROM in rom folder.
Downloads:
Download from here.
Credits:
XDA:DevDB Information
FTF-2-Zip, a Tool/Utility for the Sony Ericsson Xperia Mini, Mini Pro, Active
Contributors
Abhinav2
Version Information
Status: Stable
Created 2013-09-28
Last Updated 2013-12-11
Click to expand...
Click to collapse
Hello
Does this tool work otherwise? Meaning convert a flashable . Zip into . Ftf?
Sent from my A0001
Hello everyone ..
Well I have two problems here that happened after I unlocked my bootloader and flashed the awesome Nemesis Kernel ( over stock firmware with Fidelity JB 2.0 rom ).
Actually I wanted to post these issues at the Nemesis thread, but due to new membership limits I couldn't, so I hope that you guys can help, and especially @nicolassp
----------------
1. Offline charging is broken. I searched for this issue and came up with that it may be due a corrupted charger file after flashing a new cwm ( the one bundled with Nemesis maybe ) over a previous cwm. I don't know if a flashable undamaged charger file could do the job or not.
2. Underclocking issue. I was trying to underclock the cpu to 800 mhz using NoFrills app, it works at the beginning, but after you lock the screen and wake the phone up again it resets to default 1 ghz! I tried other cpu control apps with the same result ( Could it be some sort of conflict with Fidelity? ).
Anyway I appreciate any help from you guys, thx in advance
oliveri5 said:
Hello everyone ..
Well I have two problems here that happened after I unlocked my bootloader and flashed the awesome Nemesis Kernel ( over stock firmware with Fidelity JB 2.0 rom ).
Actually I wanted to post these issues at the Nemesis thread, but due to new membership limits I couldn't, so I hope that you guys can help, and especially @nicolassp
----------------
1. Offline charging is broken. I searched for this issue and came up with that it may be due a corrupted charger file after flashing a new cwm ( the one bundled with Nemesis maybe ) over a previous cwm. I don't know if a flashable undamaged charger file could do the job or not.
2. Underclocking issue. I was trying to underclock the cpu to 800 mhz using NoFrills app, it works at the beginning, but after you lock the screen and wake the phone up again it resets to default 1 ghz! I tried other cpu control apps with the same result ( Could it be some sort of conflict with Fidelity? ).
Anyway I appreciate any help from you guys, thx in advance
Click to expand...
Click to collapse
2. If you installed CWM before flashing nemesis than that is why you cannot charge offline, known problem, and it is still active BTW if you wait after nemesis CWM turn inactive pressing the volume down will bring up old CWM.
To fic this simply copy stock chargemon to /system/bin/ and set permissions to 755.
2. The ROM mod may have installed scripts that change cpu max/min frequency.
Thanks very much Chike, btw, can you kindly upload this file to me? ( and if it's a flashable zip I would appreciate this very much ).
And if it's a script by Fidelity that is causing the clocking issue, where could it be so that I can modify it?
oliveri5 said:
Thanks very much Chike, btw, can you kindly upload this file to me? ( and if it's a flashable zip I would appreciate this very much ).
And if it's a script by Fidelity that is causing the clocking issue, where could it be so that I can modify it?
Click to expand...
Click to collapse
Are you 6.2.A.1.100 based ROM?
The file can be extracted from system.sin in the ftf file, if not I can upload the one from my phone.
I don't know that ROM, I am guessing one of the files in /etc/init.d/ search for "/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" and comment it out ("#" at the beginning of line.)
ChikeD said:
Are you 6.2.A.1.100 based ROM?
The file can be extracted from system.sin in the ftf file, if not I can upload the one from my phone.
I don't know that ROM, I am guessing one of the files in /etc/init.d/ search for "/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" and comment it out ("#" at the beginning of line.)
Click to expand...
Click to collapse
Yes please upload it for me because I don't have the ftf at the moment and my internet connection is so bad ..
Also I uploaded the screen-state script so that you take a look at it ..
oliveri5 said:
Yes please upload it for me because I don't have the ftf at the moment and my internet connection is so bad ..
Also I uploaded the screen-state script so that you take a look at it ..
Click to expand...
Click to collapse
You see the lines
Code:
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $max_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
and
Code:
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
You can simply comment the out or replace $max_freq with different value
Code:
#max_freq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`;
max_freq="800000"
Rename old chargemon to chargemon.cwm in case you choose to use stock kernel again, and change it's permissions to 644 (no execute bit) copy chargemon to /system/bin and set permissions to 755 (read all, write owner, execute all)
ChikeD said:
You see the lines
Code:
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $max_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
and
Code:
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
You can simply comment the out or replace $max_freq with different value
Code:
#max_freq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`;
max_freq="800000"
Rename old chargemon to chargemon.cwm in case you choose to use stock kernel again, and change it's permissions to 644 (no execute bit) copy chargemon to /system/bin and set permissions to 755 (read all, write owner, execute all)
Click to expand...
Click to collapse
You are right.. The script sets the max speed of cpu and there is no problem with Nemesis Kernel.Thank you
Thank You!
It worked! Thank you very much Chike and yes nicolassp your kernel is working like a charm!
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
looking for the same
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
me too looking for the same thing ..how to extract from or decompile .backup file which we get thru recovery.
hi loverboyritesh :: i and you are in same position.. but some advaaanced users are here that we are telling rumors and lies.. dont worry bro.. even i'm trying to get solution.. will tel you after geeing one.. Still no one can tell me hoe to extract .BACKUP file..
same
i am looking for how to reinstall .backup myself so i can have my original rom install.
but i have notice my .backup is 700+mb while custom rom is 200+mb
do you know how to?
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
same here. dunno how to open and extract the files from a .backup file. hoping you know already
siiingkeeet said:
same here. dunno how to open and extract the files from a .backup file. hoping you know already
Click to expand...
Click to collapse
Nope.. Still i'm having that file but no one knew
reena0307 said:
Nope.. Still i'm having that file but no one knew
Click to expand...
Click to collapse
been searching for 5 days now :<
not a single answer found on google and forums
cant even post a new thread yet. just joined
hope someone will drop by this thread
still no solution?
got same problem here
Got a bootloop issue with an ASUS MeMo Pad 7 HD and I've booted in recovery <3e> to make a backup.
I've got a userdata_YYYYMMDD_HHMMSS.backup. I tried opening it with a bunch of tools like unyaffs, abe (Android backup extractor), going live on the file using linux tools (open as 7zip, zip, rar, tar, tar.gz, gz, bz2 , mount as iso, ext4 and so on....)
Still no luck :-/
Only clue is that the file seems compressed. During the backup under recovery, it told me 3600MB to backup and the file userdata_xxxxxxxx_xxxxxx.backup show only 2.61GB
I did this backup 3 time to ensure there were no corruption during the write process from the pad and did again the same "tests" to open the file...Not better.
If any dev' have any clue of the file format, I'd be glad to help
It doesn't seem to be a valid unix img file. Tried mounting it to no avail. When it's restored by the recovery it also extracts the individual files because i fails on one in my case and stops the entire restore... I tried unzipping it, changed extension to ,jar, .tar, .zip, etc., none of them are recognised...amazing for a standard android feature to find so little info about it
Any solution?
I called Alcatel's technical service today and they told me that you can use the backup file only from the phone. Mine gives me the following error when I try to restore it: Error Magic header
If anyone knows how to unpack the backup file I would be more than grateful.
It's a 512 byte header in front of a "tar.gz"
hexdump -C userdata_xxxxxxxx_yyyyyy.backup | lessshowed the magical zip header "1f8b0800 00000000" at offset 0x200
So, skipping 512 bytes, the rest can be gunzip | tar
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
Sir ektoric what d u mean on ur post?
Sorry cant understand it..
Can u please d a step by step procedure? Please...pls...plss
Thanks in advance...
Steps?
@ektoric sir im a noob in this... Can u show a step by step procedure?
@killen00 sorry, I assume you have a linux machine (or have access to one). The command is actually all there is to it.
Code:
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
If you don't have a linux machine available, might I suggest one of the many distros of your choice, most of which have LiveCDs which you can run without installing.
script for gunzip method
maybe on xda it is common sense, but for me it was necessary to know, that these stock android recovery extracted files can be restored with nandroid custom recovery, if you simply repack them into tar archive.
i put this two command lines in a dirty shell script (extract + repack as tar).
thanks to ektoric figuring out his gunzip method!
edit: notamamasboy's mount method added (but not tested yet). if script not works come back few days later, download again and check version, maybe it has changed meanwhile.
with this you're able to transfer data of non-rooted phone to (rooted) similar one.
this is useful in case touchscreen is broken, you haven't custom recovery installed, usb-debugging is disabled and connecting usb-otg-mouse doesn't work.
tested on my Archos 50 b Oxygen (Mediatek MT6582).
it works for me, feel free to improve, port to busybox and publish. no support. use at own risk.
edit: bckp2cwm.sh is deprecated it is FOR JELLY BEAN ONLY (no selinux support)
a newer (selinux) version bckp2win.sh for TWRP you can find here:
http://forum.xda-developers.com/showthread.php?t=3775129
How did you go about determining the magic number found at 0x200? My hexdump output does not have that magic number (1f 8b) in any instance. Leads me to believe my backup is not a tar file. Any suggestions then?
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
ektoric said:
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
Click to expand...
Click to collapse
Even more peculiarly, two backups were created a .backup and a .backup2, I wonder if combining with cat I can get somewhere...
Hey guys, i just guessing some people out there didn't want to use custom rom because, of course, BUGS, so they stay with stock.
But they also complains about limitations of stock, which is the stock is odexed, knox-enabled, and a lot of useless apps. But don't worry, i'll give you guys a guide to deodex, root, remove knox, and debloat your stock rom.
Requirements:
Put it in your PC
ODIN
TWRP
Your firmware for your baseband
Lordroid Batch Deodexer
Ext4Unpacker
Put it in your phone's external SD card [ Do this first ]
Deodexed flashable zip ( you will put it after you deodex your firmware at your PC )
Knox-Free Script
Titanium Backup Pro [ You'll use this app for debloat ]
Material Emulator [ it's terminal emulator ][ For extra guide ]
[ For Testing ] S7 SystemUI Mod
SuperSU flashable zip
BusyBox flashable zip
Extra :
Xposed Installer
Xposed Framework
Ok, let's get started.
First Guide, Create a Deodexed flashable zip:
Using winrar/any compressed file manager, extract your system.img.ext4 from your firmware
Create a folder named system, then open your ext4unpacker, browse where did you put the system.img.ext4, and extract app folder, framework folder, priv-app folder, and build.prop from system.img.ext4 to system folder
Now open Lordroid Batch Deodexed, tick zipalign and resign APK, and browse your system folder
It'll ask you how many the task should be executed at once, choose 2
It'll take a while, just relax and do something else while waiting
After it's done, click create flashable zip and name your deodexed flashable zip
you'll get your flashable zip at your Deodexer tool folder/ flashable_zips_out
Now put it in your phone, and make sure the rest of second part of requirements are inside your external SD card
Second guide, let's do all of them at once!!!! :
Power off your phone, open ODIN first and reboot your phone to download mode [ Press volume down+Home+Power, after that there will be a warning, press volume up]
Flash your firmware, after flashing done, an android logo appears for applying changes, when it still appears, press volume up+home+power quickly for entering stock recovery mode
after stock recovery entered, choose wipe data and cache partition
choose power down, then enter download mode again
with odin, flash twrp, and enter recovery mode as soon as possible as the flashing is quickly done
you'll be in twrp recovery, for now just reboot to system [IMPORTANT = Don't flash anything yet or get ready for some bootloop on your phone]
Do the first setup, and after that turn off your phone and enter recovery mode again
Now, flash all the flashable zip : order : deodexed flashable zip > [optional=if you decided to install it] ,knox free script, xposed framework, ,busybox, supersu, S7 SystemUI
Now reboot, and sit back and let the magic of deodex doing it.
after your homescreen showed up, congrats, 2/3 part of this guide is completed!!!!!
And.... the last guide is debloat your rom
Install Titanium Backup Pro, Xposed Installer [ if you decided to install xposed ], and Material Emulator
Open Titanium Backup Pro, and give it root permission
Uninstall these apps ( you can add more if you want ) : Drive, Books, Kiosk, Play Music, Google+, Hangouts, Galaxy Apps, S Lime, Galaxy Gift and Smart Manager
Reboot, and congratulations, you've done all the main guide!! Time for the Extra Guide!!!
Extra Guide: Make your SELinux permissive permanently ( useful if you wanna use any Sound Mods )
Open Material Emulator, type su , and give the root permission
Now do this commands per line:
mount -o remount,rw /system
mkdir /system/su.d [ if you find error : su.d already exists, just ignore it ]
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
After you done with it , go to settings > about to see if you have done it right
If it's permissive , then voila!!! you've done all the guides with a big success!!!
Download Links [Zips only, you can search the apks on Google]:
Knox Free Script : https://www.androidfilehost.com/?fid=24052804347792751
SuperSU : http://download.chainfire.eu/999/SuperSU/BETA-SuperSU-v2.77-20160827190633.zip
BusyBox : https://filescdn.com/cqxezkyyc8qr
TWRP : https://filescdn.com/m37eo75ol0b2
Ext4Unpacker: https://filescdn.com/noefidrz00nq
Lordroid Batch Deodexer: https://filescdn.com/qjpm1u4rff9n
Xposed Framework : https://filescdn.com/gbu6e8r2co2n
ODIN : https://filescdn.com/oz8iaxilvzac
S7 SystemUI : https://drive.google.com/file/d/0B0AGKxXT-aJwSGc3a19SXzlnQzQ/view?usp=sharing
:good: Big Thanks to :
TEKHD, Cherniavsky94w, Chainfire , osmOsis, [Has.007, rovo89, dkcldark, and arter97], Fahd95, and lord-ralf-adolf.
Important note: S7 SystemUI, TWRP, & Xposed framework that i provided is only for Lollipop 5.0.2 (spesifically builded for Grand Prime), but the rest is available for all samsung devices
Well
actually no one say thanks to you
so thanks
Very clear and simple guide, and pretty useful,
i am going to do everything, i love to mod my grand prime's system.
Stock SS after all guide done
D.R-Ult.Googler said:
Hey guys, i just guessing some people out there didn't want to use custom rom because, of course, BUGS, so they stay with stock.
But they also complains about limitations of stock, which is the stock is odexed, knox-enabled, and a lot of useless apps. But don't worry, i'll give you guys a guide to deodex, root, remove knox, and debloat your stock rom.
Requirements:
Put it in your PC
ODIN
TWRP
Your firmware for your baseband
Lordroid Batch Deodexer
Ext4Unpacker
Put it in your phone's external SD card [ Do this first ]
Deodexed flashable zip ( you will put it after you deodex your firmware at your PC )
Knox-Free Script
Titanium Backup Pro [ You'll use this app for debloat ]
Material Emulator [ it's terminal emulator ][ For extra guide ]
[ For Testing ] S7 SystemUI Mod
SuperSU flashable zip
BusyBox flashable zip
Extra :
Xposed Installer
Xposed Framework
Ok, let's get started.
First Guide, Create a Deodexed flashable zip:
Using winrar/any compressed file manager, extract your system.img.ext4 from your firmware
Create a folder named system, then open your ext4unpacker, browse where did you put the system.img.ext4, and extract app folder, framework folder, priv-app folder, and build.prop from system.img.ext4 to system folder
Now open Lordroid Batch Deodexed, tick zipalign and resign APK, and browse your system folder
It'll ask you how many the task should be executed at once, choose 2
It'll take a while, just relax and do something else while waiting
After it's done, click create flashable zip and name your deodexed flashable zip
you'll get your flashable zip at your Deodexer tool folder/ flashable_zips_out
Now put it in your phone, and make sure the rest of second part of requirements are inside your external SD card
Second guide, let's do all of them at once!!!! :
Power off your phone, open ODIN first and reboot your phone to download mode [ Press volume down+Home+Power, after that there will be a warning, press volume up]
Flash your firmware, after flashing done, an android logo appears for applying changes, when it still appears, press volume up+home+power quickly for entering stock recovery mode
after stock recovery entered, choose wipe data and cache partition
choose power down, then enter download mode again
with odin, flash twrp, and enter recovery mode as soon as possible as the flashing is quickly done
you'll be in twrp recovery, for now just reboot to system [IMPORTANT = Don't flash anything yet or get ready for some bootloop on your phone]
Do the first setup, and after that turn off your phone and enter recovery mode again
Now, flash all the flashable zip : order : deodexed flashable zip > [optional=if you decided to install it] ,knox free script, xposed framework, ,busybox, supersu, S7 SystemUI
Now reboot, and sit back and let the magic of deodex doing it.
after your homescreen showed up, congrats, 2/3 part of this guide is completed!!!!!
And.... the last guide is debloat your rom
Install Titanium Backup Pro, Xposed Installer [ if you decided to install xposed ], and Material Emulator
Open Titanium Backup Pro, and give it root permission
Uninstall these apps ( you can add more if you want ) : Drive, Books, Kiosk, Play Music, Google+, Hangouts, Galaxy Apps, S Lime, Galaxy Gift and Smart Manager
Reboot, and congratulations, you've done all the main guide!! Time for the Extra Guide!!!
Extra Guide: Make your SELinux permissive permanently ( useful if you wanna use any Sound Mods )
Open Material Emulator, type su , and give the root permission
Now do this commands per line:
mount -o remount,rw /system
mkdir /system/su.d [ if you find error : su.d already exists, just ignore it ]
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
After you done with it , go to settings > about to see if you have done it right
If it's permissive , then voila!!! you've done all the guides with a big success!!!
Download Links [Zips only, you can search the apks on Google]:
Knox Free Script : https://www.androidfilehost.com/?fid=24052804347792751
SuperSU : http://download.chainfire.eu/999/SuperSU/BETA-SuperSU-v2.77-20160827190633.zip
BusyBox : https://filescdn.com/cqxezkyyc8qr
TWRP : https://filescdn.com/m37eo75ol0b2
Ext4Unpacker: https://filescdn.com/noefidrz00nq
Lordroid Batch Deodexer: https://filescdn.com/qjpm1u4rff9n
Xposed Framework : https://filescdn.com/gbu6e8r2co2n
ODIN : https://filescdn.com/oz8iaxilvzac
S7 SystemUI : https://drive.google.com/file/d/0B0AGKxXT-aJwSGc3a19SXzlnQzQ/view?usp=sharing
:good: Big Thanks to :
TEKHD, Cherniavsky94w, Chainfire , osmOsis, [Has.007, rovo89, dkcldark, and arter97], Fahd95, and lord-ralf-adolf.
Click to expand...
Click to collapse
firmware has md5 format and can only executed by Odin. so, how to deodex stock firmware? or how to change firmware to rom?
Other Dimitri said:
firmware has md5 format and can only executed by Odin. so, how to deodex stock firmware? or how to change firmware to rom?
Click to expand...
Click to collapse
plz.. next time don't quote the whole OP :silly: open the md5 with winrar, then extract the system.img.ext4 file
i cant open the md5 with winRAR
Other Dimitri said:
i cant open the md5 with winRAR
Click to expand...
Click to collapse
right click on the md5, click open with...
Other Dimitri said:
i cant open the md5 with winRAR
Click to expand...
Click to collapse
now i can open it haha thanks
---------- Post added at 05:22 PM ---------- Previous post was at 04:47 PM ----------
Is Lordroid Batch Deodex same as Lordroid ONE Deodexer?
Other Dimitri said:
now i can open it haha thanks
---------- Post added at 05:22 PM ---------- Previous post was at 04:47 PM ----------
Is Lordroid Batch Deodex same as Lordroid ONE Deodexer?
Click to expand...
Click to collapse
yup
D.R-Ult.Googler said:
Hey guys, i just guessing some people out there didn't want to use custom rom because, of course, BUGS, so they stay with stock.
But they also complains about limitations of stock, which is the stock is odexed, knox-enabled, and a lot of useless apps. But don't worry, i'll give you guys a guide to deodex, root, remove knox, and debloat your stock rom.
Click to expand...
Click to collapse
hello I read your tutorial and wanna try it to my friend phone, but I'm not really sure that the phone compatible with your tutorial, so I wanna ask some(lot) of things b4 started (pardon about lot of my noob question )
here's the baseband firmware : G530HXCS1BQA1
1. is the bold one means "XCU firmware(fortuneve3g)", kinda confused since its write XCS in here link
2. could you please recommend me good stock firmware version
these are what I understand from your tutorial, please tell me if i'm misunderstand
for the first guide
3. so I have to download stock firmware for my baseband version, then transform it to Deodexed flashable zip using : WinRAR, ext4unpacker, Landroid Batch Deodexed(Lordroid ONE Deodexer)
4. is it possible to put deodexed flashable zip and second part requirements inside internal SD card?
thank you in advance
fanasio said:
hello I read your tutorial and wanna try it to my friend phone, but I'm not really sure that the phone compatible with your tutorial, so I wanna ask some(lot) of things b4 started (pardon about lot of my noob question )
here's the baseband firmware : G530HXCS1BQA1
1. is the bold one means "XCU firmware(fortuneve3g)", kinda confused since its write XCS in here link
2. could you please recommend me good stock firmware version
these are what I understand from your tutorial, please tell me if i'm misunderstand
for the first guide
3. so I have to download stock firmware for my baseband version, then transform it to Deodexed flashable zip using : WinRAR, ext4unpacker, Landroid Batch Deodexed(Lordroid ONE Deodexer)
4. is it possible to put deodexed flashable zip and second part requirements inside internal SD card?
thank you in advance
Click to expand...
Click to collapse
you can do this in any lollipop firmware of Grand Prime
D.R-Ult.Googler said:
you can do this in any lollipop firmware of Grand Prime
Click to expand...
Click to collapse
thankyou, i'll try it as soon as the firmware download finished
fanasio said:
hello I read your tutorial and wanna try it to my friend phone, but I'm not really sure that the phone compatible with your tutorial, so I wanna ask some(lot) of things b4 started (pardon about lot of my noob question )
here's the baseband firmware : G530HXCS1BQA1
1. is the bold one means "XCU firmware(fortuneve3g)", kinda confused since its write XCS in here link
2. could you please recommend me good stock firmware version
these are what I understand from your tutorial, please tell me if i'm misunderstand
for the first guide
3. so I have to download stock firmware for my baseband version, then transform it to Deodexed flashable zip using : WinRAR, ext4unpacker, Landroid Batch Deodexed(Lordroid ONE Deodexer)
4. is it possible to put deodexed flashable zip and second part requirements inside internal SD card?
thank you in advance
Click to expand...
Click to collapse
you can, but i recommend to put it in external sdcard just in case to prevent it got deleted if you wanna do factory reset b4 start deodexing
D.R-Ult.Googler said:
you can, but i recommend to put it in external sdcard just in case to prevent it got deleted if you wanna do factory reset b4 start deodexing
Click to expand...
Click to collapse
I follow your guidance and it work really well
thank you very much the devices rooted flawlessly
thanks
thanks and its great tutorial...
some ask ..
-can this methode use in marsmellow stock rom?
-if not, could you please recommend what methode to use..
Thanks
ademb said:
thanks and its great tutorial...
some ask ..
-can this methode use in marsmellow stock rom?
-if not, could you please recommend what methode to use..
Thanks
Click to expand...
Click to collapse
maybe... but use fulmics deodexer instead
and don't use the test file