Guyz, Do not ever flash the zip file obtained from UOT kitchen directly to the galaxy r. The Manifest and settings.uot files in the UOT zip file have the wrong configurations ie. not compatible with our phone. The assumed busybox location in the settings and Manifest file is wrong as a result when you flash the zip file it will only delete the original framework-res.apk, systemui.apk and twframework.apk but would not replace them with the modified ones from the UOT zip file. So when you reboot.....---> BOOT LOOP...dead end. I would suggest you to manually push the modified files to their respective locations. I myself ended up into a boot loop yesterday and as luck would have it even my nandroid backup had become corrupt...so had to flash a stock rom through odin..atleast it saved me.
Thanks saurabh.khare for the info.
i've used UOT kitchen many time and i didn't face any problem, when you are flashing the wrong zip file you will have these kind of issues for eg: once i've uploaded the stock ROM framework and flashed it on custom ROM then i faced these kind of issue's..
Yup me too, I've flashed uot-files several times. Never faced such issues.
mj.vikram said:
i've used UOT kitchen many time and i didn't face any problem, when you are flashing the wrong zip file you will have these kind of issues for eg: once i've uploaded the stock ROM framework and flashed it on custom ROM then i faced these kind of issue's..
Click to expand...
Click to collapse
Buddy I'm very much sure that I did nothing wrong. I extracted the files out of a rooted stock ROM(XWKI5) and flashed the cooked zip file over the same rooted Stock ROM through CWM. I have attached the file for you reference...If you could go through and point out where I went wrong I would be very glad
saurabh.khare1000 said:
Guyz, Do not ever flash the zip file obtained from UOT kitchen directly to the galaxy r. The Manifest and settings.uot files in the UOT zip file have the wrong configurations ie. not compatible with our phone. The assumed busybox location in the settings and Manifest file is wrong as a result when you flash the zip file it will only delete the original framework-res.apk, systemui.apk and twframework.apk but would not replace them with the modified ones from the UOT zip file. So when you reboot.....---> BOOT LOOP...dead end. I would suggest you to manually push the modified files to their respective locations. I myself ended up into a boot loop yesterday and as luck would have it even my nandroid backup had become corrupt...so had to flash a stock rom through odin..atleast it saved me.
Click to expand...
Click to collapse
I have flashed files from UOT several times on Galaxy R without any errors(Both Stock Odex and Deodex ones). Not sure why you had issues.
Want to know how to make CWM flashable zips using phone? Here's what you have to do. I have attached a sample zip file which consists of two folders viz. META-INF and system. Now download PowerGrasp.apk from the attached files. Install it, open it and then copy any app which you want as a flashable file. And then paste it in a new folder named "app" under the "system" folder in the "sample CWM.zip" file. Now the compressor of PowerGrasp will pop up. Set the compression level to 6. Now compress it. And you're done.
Now you've successfully made your own cwm flashable zip file. Use CWM recovery to flash.
{Neither of the attached files is my development. I got these files from a friend and posted these to help others who want to make flashable zips on phone}
In many tutorial i'm seeing some flashable zip files that can be flashed through recovery.
I have just flashed supersu which i'll need always.
But there are apps like xperia walkman & other app which require to flash zip through recovery.
What about removing them completely if i want in future.
Wondering if anybody around here has some experience on using SVADeodexerForArt?
Trying to deodex D6603_Customized US_1288-7827_23.4.A.1.232_R6C and from what I gathered this is the tool to use, but been bouncing from thread to thread trying to understand how to make use of it and the more I read the more confusing it has become and I'm still at square one...
Anybody willing to shade to light and give direction on how to proceed?
Thanks
-Deodex-
Ok, so after a few days of reading I figured how to deodex my rom, took the long way since I didn't have the rom on my phone, just started from the xperifirm file...
Want to give a big THANKS @serajr for answering my questions and letting me use his zip to add my files for flashing!
This deodex zip is only for the D6603_Customized US_1288-7827_23.4.A.1.232_R6C firmware with root and recovery so be sure you're on that exact firmware before flashing!
-BACK UP before you even think of flashing this-
there is no debloat in the zip , you'll end up with a full stock D6603_Customized US_1288-7827_23.4.A.1.232_R6C deodexed, rooted and dualrecovery firmware
just flash the zip through recovery, wipe cache and dalvik and then boot...
get the deodex zip to flash here
-DM- said:
Ok, so after a few days of reading I figured how to deodex my rom, took the long way since I didn't have the rom on my phone, just started from the xperifirm file...
Want to give a big THANKS @serajr for answering my questions and letting me use his zip to add my files for flashing!
This deodex zip is only for the D6603_Customized US_1288-7827_23.4.A.1.232_R6C firmware with root and recovery so be sure you're on that exact firmware before flashing!
-BACK UP before you even think of flashing this-
there is no debloat in the zip , you'll end up with a full stock D6603_Customized US_1288-7827_23.4.A.1.232_R6C deodexed, rooted and dualrecovery firmware
just flash the zip through recovery, wipe cache and dalvik and then boot...
get the deodex zip to flash here
Click to expand...
Click to collapse
Hello there,
Can you please share how you did that? I am not able to find any way.
I wanna deodex D6653 firmware 23.4.A.1.232 Customized IN
I have .ftf, PRF Creator and SVA Deodexer
Thanks in advance
Mohitash said:
Hello there,
Can you please share how you did that? I am not able to find any way.
I wanna deodex D6653 firmware 23.4.A.1.232 Customized IN
I have .ftf, PRF Creator and SVA Deodexer
Thanks in advance
Click to expand...
Click to collapse
First make sure that you have the firmware you want to deodex, rooted with recovery and installed on your phone already so in your case D6653 firmware 23.4.A.1.232 Customized IN , if not then create a prerooted zip with that ftf file, SuperSu and latest dual recovery with PRFcreator then flash it and boot....Once that exact firmware is on your phone, you can follow those steps below to create a deodex zip.
Here is the process:
-download the zip that I provided in this thread (you'll need it later to swap my files with yours)
-open the ftf with 7-Zip to copy the system.sin file
-then use Flashtool Sin Editor to extract data to get System.ext4
-from there, use ext2explore (download it here) to open the system.ext4
-Once you opened system.ext4, locate those 3 folders (app, framework and priv-app) and build.prop
-create a folder called deodex on your C drive (so C:\deodex) and copy those 3 folders mentioned above and the build.prop file to it
-then move SemcGenericUxpRes folder from framework folder to app folder and take the 2 containing folders from vendor\app and move them to the app folder as well
- then run SVADeoderForArt.exe and selected the path to C:\deodex folder, check deodexing framework, app and private-app, let the tool run (it should tell you if it ran without errors when done)
-now you should have app, dex, framework, odex and priv-app folders (inside the SVADeodexerforart folder) after the tools finished the deodexing process (you can delete the dex and odex as they're not needed anymore)...now move SemcGenericUxpRes folder back to framework folder...also move back the 2 folders that you took from vendor\app, just put them anywhere on your desktop you're going to need them in a minute
-now when you open the deodex zip that you first downloaded, go into the system folder and you'll see 4 folders, app, framework, priv-app and vendor....delete the 3 folders app (but before, move the supersu folder from my app folder to your app folder, otherwise you'll end up without supersu) , framework and priv-app folders and move your 3 corresponding folders in there...now open vendor\app and delete the 2 folders and put yours instead
-your deodex zip should be good to flash now, put it on your sdcard...reboot to recovery, choose your zip to flash , then clear cache and dalvik cache and then boot....now you should have a full stock deodexed D6653 firmware 23.4.A.1.232 Customized IN (if you want to debloat, remove what you don't want from the app and private app folder in the zip before flashing, but you're on your own for that)
And as always make a backup before you start all this
Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes
-DM- said:
First make sure that you have the firmware you want to deodex rooted with recovery installed on your phone..............Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes
Click to expand...
Click to collapse
Thanks a lot for taking your time to write this and to give me good guide. This will help others too.
Ok i will follow the guide and now i am good to go. In case, any help needed, i will post here
And i think you saying to download your deodexed.zip only for meta inf and SuperSU, so i am not going to download that because i can do it myself so why to download ~800mb zip
And ya, Big thanks to @serajr. I dont know where to post exactly. So i am thanking you @serajr here.
Thanks and Regards
Mohitash
Mohitash said:
And i think you saying to download your deodexed.zip only for meta inf and SuperSU, so i am not going to download that because i can do it myself so why to download ~800mb zip
Thanks and Regards
Mohitash
Click to expand...
Click to collapse
yes, but looks like that you know what you're doing so you should be good to go
-DM- said:
yes, but looks like that you know what you're doing so you should be good to go
Click to expand...
Click to collapse
Ya, you got me right. May be you checked my profile or you can check now my history on XDA
I am just very very new to Sony and lollipop
Sent you pm.....
Regards
Mohitash
-DM- said:
First make sure that you have the firmware you want to deodex, rooted with recovery and installed on your phone already so in your case D6653 firmware 23.4.A.1.232 Customized IN , if not then create a prerooted zip with that ftf file, SuperSu and latest dual recovery with PRFcreator then flash it and boot....Once that exact firmware is on your phone, you can follow those steps below to create a deodex zip.
Here is the process:
-download the zip that I provided in this thread (you'll need it later to swap my files with yours)
-open the ftf with 7-Zip to copy the system.sin file
-then use Flashtool Sin Editor to extract data to get System.ext4
-from there, use ext2explore (download it here) to open the system.ext4
-Once you opened system.ext4, locate those 3 folders (app, framework and priv-app) and build.prop
-create a folder called deodex on your C drive (so C:\deodex) and copy those 3 folders mentioned above and the build.prop file to it
-then move SemcGenericUxpRes folder from framework folder to app folder and take the 2 containing folders from vendor\app and move them to the app folder as well
- then run SVADeoderForArt.exe and selected the path to C:\deodex folder, check deodexing framework, app and private-app, let the tool run (it should tell you if it ran without errors when done)
-now you should have app, dex, framework, odex and priv-app folders (inside the SVADeodexerforart folder) after the tools finished the deodexing process (you can delete the dex and odex as they're not needed anymore)...now move SemcGenericUxpRes folder back to framework folder...also move back the 2 folders that you took from vendor\app, just put them anywhere on your desktop you're going to need them in a minute
-now when you open the deodex zip that you first downloaded, go into the system folder and you'll see 4 folders, app, framework, priv-app and vendor....delete the 3 folders app (but before, move the supersu folder from my app folder to your app folder, otherwise you'll end up without supersu) , framework and priv-app folders and move your 3 corresponding folders in there...now open vendor\app and delete the 2 folders and put yours instead
-your deodex zip should be good to flash now, put it on your sdcard...reboot to recovery, choose your zip to flash , then clear cache and dalvik cache and then boot....now you should have a full stock deodexed D6653 firmware 23.4.A.1.232 Customized IN (if you want to debloat, remove what you don't want from the app and private app folder in the zip before flashing, but you're on your own for that)
And as always make a backup before you start all this
Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes
Click to expand...
Click to collapse
I understand the problem but somehow I do follow instructions whose results have been bootloop
đạt gao ô said:
I understand the problem but somehow I do follow instructions whose results have been bootloop
Click to expand...
Click to collapse
Sent you a pm
- Edit - Read post 2 first
I Deodexed my framework folder with Super R's kitchen and patched services jar file to enable signature spoofing for MicroG. The flashable zip should wipe your framework folder and replace it with the new one. I can't test it right now, but try it out if you want. If the flashable doesn't work, and you want to use it, just extract the zip and use file manager in recovery to delete your whole framework folder and copy the new one there, (probably a good idea to wipe dalvik/cache).
Note about deodexing - could possibly make certain aspect of the phone slower. Only thing I have noticed so far is longer boot time...
https://mega.nz/#!E58U2AJb!j0XIq0veM3XdxjMCvjBoOZwQFRIsz3cfvi-rbrSyCU0
Update - so I tried it, and it doesn't flash properly, (some error in the script), but I also found out that it's much more stable to just replace the services jar with the deodexed one, and leave the rest of the framework as-is. So if you want to use MicroG, just extract the services jar from the zip, and then use file manager in recovery to delete the current one, and also delete the 3 services files, (odex, vdex, and art), from /system/framework/oat/arm64.
Then you can flash MicroG...
Zip attachment in first post is a custom Magisk module that was made with smali patcher. It replaces services jar file with a patched one that is deodexed (see above for instructions)...