u18 android smart watch - Other SmartWatches

hello everyone how are you
i have a q dose anyone have mods or root or anything for the smart watch u18 it have android 4.4 but not pure android it dose not have playstore but it can install some app via aptoid but it can not install playstore or watch faces
so any help installing play store or enableing installing watch faces will be great
thanks in advance

Is it possible to access the recovery on a smart watch? Maybe you can install gapps package there.

Hi, I also have one of these.
Any info gratefully accepted.
It appears to be trying to update today but fails the download each time U18_V2.4 same with the USmart app for the phone.
Again any info appreciated.

the steve said:
Is it possible to access the recovery on a smart watch? Maybe you can install gapps package there.
Click to expand...
Click to collapse
i dont know

KeltikRellik said:
Hi, I also have one of these.
Any info gratefully accepted.
It appears to be trying to update today but fails the download each time U18_V2.4 same with the USmart app for the phone.
Again any info appreciated.
Click to expand...
Click to collapse
yeah me too

Pushing buttons during boot does't work I think. On my smartphone it is possible to reboot into recovery with the extended restart menu. This must be activated in developer options. Maybe the watch has this option too?

Update, managed to download u18_v2.4.zip using the app on the phone.
It crashed the watch and left it in a set up mode with red exclamation in a triangle.
Rebooted watch and it's back to normal with no update.
Copied u18_v2.4.zip to PC and tried to extract, multiple errors
Code:
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\fstab.fat.nand
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\system
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sys
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\ueventd.rc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbchk
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbchk\sbchk
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbchk\sec_chk.sh
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\fstab
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\proc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\FWUpgradeInit.rc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\factory_init.rc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\keys
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_installing_overlay07.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\indeterminate05.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_installing_overlay05.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_installing_overlay01.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_installing.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\indeterminate02.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\erasing_text.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\error_text.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_installing_overlay06.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\installing_text.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_installing_overlay03.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\progress_empty.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\progress_fill.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\indeterminate04.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\indeterminate03.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_installing_overlay04.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\no_command_text.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_installing_overlay02.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\indeterminate01.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\icon_error.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\indeterminate06.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\res\images\font.png
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sepolicy
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\meta_init.project.rc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\seapp_contexts
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\data
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbin
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbin\gzip
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbin\watchdogd
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbin\adbd
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbin\healthd
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbin\recovery
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\sbin\ueventd
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\init.rc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\property_contexts
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\fstab.nand
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\dev
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\init
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\file_contexts
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\fs.rc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\meta_init.modem.rc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\etc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\etc\recovery.fstab
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\meta_init.rc
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\default.prop
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create folder C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\tmp
! The system cannot find the path specified.
C:\Users\Jason\Desktop\rebuilt.U18_V2.4.zip: Cannot create C:\Users\Jason\Desktop\rebuilt.U18_V2.4\RECOVERY\RAMDISK\factory_init.project.rc
! The system cannot find the path specified.
Also have a new folder on watch "USMART" with sub folder "update"
Any ideas? Should I dump the .zip files in update?

what I have managed so far
I have a U18 as well, same problems, as posted above.
I have accessed recovery with adb reboot recovery, there is no options menu
I have accessed fastboot with adb reboot bootloader there is no options menu
I have also managed shell command,
I did manage to get a clean download of the U18_V2.4.zip , (357.8 meg) to the phone but not sure about the phone to watch upload as it auto reboots and crashes in the recovery flash mode.
the USMART/update/ folder on the watch is where the phone transfer's the update to
the /bluetoothConnect/downlown/ folder is where the phone (throught USMART) saves the update
https://www.dropbox.com/s/c2191tq3xt8ii48/U18_V2.3.zip?dl=0
https://dl.dropboxusercontent.com/u/27107959/U18_V2.4.zip
https://dl.dropboxusercontent.com/u/27107959/usmart-v1.4.apk
Gerry

ghenton said:
I have a U18 as well, same problems, as posted above.
I have accessed recovery with adb reboot recovery, there is no options menu
I have accessed fastboot with adb reboot bootloader there is no options menu
I have also managed shell command,
I did manage to get a clean download of the U18_V2.4.zip , (357.8 meg) to the phone but not sure about the phone to watch upload as it auto reboots and crashes in the recovery flash mode.
the USMART/update/ folder on the watch is where the phone transfer's the update to
the /bluetoothConnect/downlown/ folder is where the phone (throught USMART) saves the update
https://dl.dropboxusercontent.com/u/27107959/U18_V2.4.zip
Gerry
Click to expand...
Click to collapse
Good idea to try adb, I didn't know if smartwatches would be adb devices. Is it an official OTA update you want to install or a custom rom? Maybe you need to install custom recovery first, have you tried twrp recovery?

it is locked down quite tightly
the steve said:
Good idea to try adb, I didn't know if smartwatches would be adb devices. Is it an official OTA update you want to install or a custom rom? Maybe you need to install custom recovery first, have you tried twrp recovery?
Click to expand...
Click to collapse
This is an official OTA update, takes 2-3 hours to download to the phone which then uploads to the watch, which reboots into recovery and then crashes in a few seconds. I have tried to root the device without success so far. There is an update to USMART the phone app that controls the whole process but it will not even download yet. I have a ticket in with support at bestgear but I have open tickets that go back months without any action. They confirm that they have received the initial ticket but then all goes quite.
Gerry

wtf?! 2-3 hours? I didn't expect that with an official OTA update... Has there be any warning during the installation, that it will last that long? Otherwise it doesn't seem right. Have you tried a factory reset in the recovery and run the update again?
Before you start any further experiments be sure you want to keep the watch. You didn't root or flash custom roms yet, so you still have warranty and could give it back.
---------- Post added at 11:03 PM ---------- Previous post was at 10:35 PM ----------
If you still want to root and install playstore on your watch, maybe this video might help you. It is not exactly your watch, but since you don't have to flash anything it might work for your device to.
https://www.youtube.com/watch?v=jAsO2hfAcn0
Notice: I don't take any responsibility if you brick your watch!

is there a way to go back to old version ?
because i think the v2.2 is very bad bluetooth and wifi

or is there a way to install update without connecting to usmart app because everytime i open it it crash

DARK_A said:
or is there a way to install update without connecting to usmart app because everytime i open it it crash
Click to expand...
Click to collapse
If you have the update file as zip on your watch, it might be possible to install it in the recovery. Depends on the recovery. TWRP recovery for example works with touch screen and has an install menu.

the steve said:
If you have the update file as zip on your watch, it might be possible to install it in the recovery. Depends on the recovery. TWRP recovery for example works with touch screen and has an install menu.
Click to expand...
Click to collapse
problem is how to go to recovery

DARK_A said:
problem is how to go to recovery
Click to expand...
Click to collapse
On the last page a user posted, it is possible by using adb.

the steve said:
wtf?! 2-3 hours? I didn't expect that with an official OTA update... Has there be any warning during the installation, that it will last that long? Otherwise it doesn't seem right. Have you tried a factory reset in the recovery and run the update again?
Before you start any further experiments be sure you want to keep the watch. You didn't root or flash custom roms yet, so you still have warranty and could give it back.
The update is 357.8 meg so it will take time, once to the phone and again from the phone to the watch, this take the longest and most likely to fail as the Bluetooth can be a little flaky. There is no warning on time but there is a progress bar. There is an option to "reset watch" in "Settings" this does a reboot/wipe/restore through recovery.
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
If you still want to root and install playstore on your watch, maybe this video might help you. It is not exactly your watch, but since you don't have to flash anything it might work for your device to.
https://www.youtube.com/watch?v=jAsO2hfAcn0
Notice: I don't take any responsibility if you brick your watch!
Click to expand...
Click to collapse
I had come across this video but it did not work. I have installed the playstore apk but it will not run. Amazon store does install and will run. One of the problems is not many apps will format for the small screen and you cannot gain access to the install buttons as they are off screen.

Trying to apply U18_V2.4.zip
I'm in the same boat as others... hoping to try out the U18 V2.4 update, but the OTA update always fails.
I have accomplished getting the V1.4 phone app installed and working. It failed to download for me, like some others have reported, but I was able to extract the APK from the U18_V2.4.zip file, and sideloaded U18_V2.4/SYSTEM/data/usmart.apk from the zip file onto my phone.
Now, here's some more clues on the failure of the OTA update on the watch. Look at /sdcard/logs/recovery/20150820_171751.log...
Here's an excerpt:
----------------------------------------------------------
update_package = /sdcard/USMART/update//U18_V2.4.zip
I:Finding update package...
I:Update location: /sdcard/USMART/update//U18_V2.4.zip
Ipening update package...
Installing update...
The update.zip is corrupted
Installation aborted.
write result : MOTA_RESULT_FILE
write result : remove_mota_file
----------------------------------------------------------
Looking for the strings "The update.zip is corrupted" and "write result : MOTA_RESULT_FILE" leads me to this webpage with the source of our recovery.c....
on github: andr3jx MTK6577 blob master bootable recovery recovery.c
Sorry I can't post a proper URL yet.
---------- Post added at 10:03 AM ---------- Previous post was at 09:41 AM ----------
Having read some more source code on github, one reason why "The update.zip is corrupted" would end up in the log is that the file is improperly signed. Ugh. This may be a dead end until the manufacturer fixes the "corrupt" update.

ghenton said:
I had come across this video but it did not work. I have installed the playstore apk but it will not run. Amazon store does install and will run. One of the problems is not many apps will format for the small screen and you cannot gain access to the install buttons as they are off screen.
Click to expand...
Click to collapse
Is it possible to login your google account with the watch? Then you could perhaps chose the apps in Playstore on your Computer and then chose to install on the watch. Or have you tried already?

The web address for the update server...
I still can't post an URL, but point your browser to 120.25.243.229 slash u18.
This is where the phone app looks for updates!
---------- Post added at 11:24 PM ---------- Previous post was at 10:30 PM ----------
I believe this is the manufacturer's website: www wtech cc slash Bluetooth-Smart-Watch_c34.html

Related

[Q] Is it spossible to chnge the system.ext2 file?

Hi,
I really like all the Android builds that use the Desire ROM as I really like the HTC Sense. However, my language isn't really supported there (The fonts exist but the formatting is bad).
I have some files that should fix the formatting, but they are meant for the original HTC Desire and are installed by going to the ROM Manager/Recovery Mode and then choosing an option called: "Install Zip from SD Card".
Since I can't go to this ROM Manager nor get into Recovery mode with the HD2 Builds I am looking for an alternate way to change the system files on the Android build I am using.
The thing is that I am having difficulties doing so.
At first I tried using EStrongs File Explorer to get root access and copy over the new files I want to change but it gave me an error that it failed.
After I couldn't make it work I started looking for ways to open and edit the system.ext2 file in Windows.
I couldn't find any program or driver that would let me change the files, but only view them so I decided to install Linux and do it from there.
I used VMware workstation to install Ubuntu on my system.
On Ubuntu I mounted the system.ext2 following the mentioned instructions here: http://forum.xda-developers.com/showpost.php?p=8001443&postcount=8
It mounted okay but it said there was 0 bytes free when I tried to overwrite the files I wanted to change.
In addition it gave me permission errors, the error was that I did not have permission to copy the files.
I am not that familiar with Linux and I tired googling for answers but couldn't find anything useful.
I would appreciate if anyone can explain how to do it, or direct me to somewhere with more details as I'm kinda stuck at the moment.
The files I wanna change are:
/framework/framework.jar
/app/.DS_Store
/app/Gallery3D.apk
/app/Mms.apk
And a few font files to /fonts
Thanks a lot!
It is best to mount the ext2 file as you suggest but instead of trying to modify the file, copy the contents into a new folder and use the genext2fs command to recreate the system.ext2 file!
Hey man, it worked perfectly.
Thanks a lot!!
By the way, is there a recommended file size for the system.ext2? Or should I just keep the original size?
Is it worth setting it bigger? Will it benefit somehow?

Help with compiling apk for framework-res

I am trying to create a custom theme, by modifying the framework-res.apk. I have been successful in porting some really cool .png files, but my problems start with the de-compiling & recompiling the .apk so I can modify the .xml & .9.png files. It seems every time I recompile my .apk it sends me in to a boot loop. I have used both APKTool and APK Manager with no luck. Here are my steps:
APK Manager:
1. Use a root explorer to copy the framework-res.apk.
2. Paste the file on my sd card.
3. Copy the file and paste it in the "place-apk-here-for-modding" folder.
4. Choose option 9 for compile.
5. Open the .xml file with Notepad++.
6. Recompile .apk using option 11.
7. Yes to "is this a system file?"
8. Yes to "keep original files & signatures"
9. Delete the files I modified from the "keep" folder and the resources.ascr file.
10. Finish the build of the .apk.
11. Copy & paste the modified .apk back to my sd card.
12. Rename the file from unsigned-framework-res.apk to framework-res.apk.
13. Use root explorer to cut & paste the modified to my /system/framework folder.
14. Reboot.
I now end up in a boot loop what am I doing wrong??
Rockstar52 said:
I am trying to create a custom theme, by modifying the framework-res.apk. I have been successful in porting some really cool .png files, but my problems start with the de-compiling & recompiling the .apk so I can modify the .xml & .9.png files. It seems every time I recompile my .apk it sends me in to a boot loop. I have used both APKTool and APK Manager with no luck. Here are my steps:
APK Manager:
1. Use a root explorer to copy the framework-res.apk.
2. Paste the file on my sd card.
3. Copy the file and paste it in the "place-apk-here-for-modding" folder.
4. Choose option 9 for compile.
5. Open the .xml file with Notepad++.
6. Recompile .apk using option 11.
7. Yes to "is this a system file?"
8. Yes to "keep original files & signatures"
9. Delete the files I modified from the "keep" folder and the resources.ascr file.
10. Finish the build of the .apk.
11. Copy & paste the modified .apk back to my sd card.
12. Rename the file from unsigned-framework-res.apk to framework-res.apk.
13. Use root explorer to cut & paste the modified to my /system/framework folder.
14. Reboot.
I now end up in a boot loop what am I doing wrong??
Click to expand...
Click to collapse
You have to sign it with 12
Lenn said:
You have to sign it with 12
Click to expand...
Click to collapse
Tried it, still boot loops at the Archos screen. I then have to do a complete format & wipe reinstalling the SDK, firmware, and the root files. I don't get it.
Lenn said:
You have to sign it with 12
Click to expand...
Click to collapse
Do not sign frameworks! How many time do I have to say this! System apps do not get signed...
Now, as far as the framework, there's two things to check. First, what XMLs have you edited? Second, instead of using root explorer to copy the framework, connect to a pc and use adb to perform these commands:
Code:
su
stop
cp /system/framework/framework-res.apk /system/framework/framework-res.old
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk
sync
start
If it continues boot-looping, you will still be connected through adb, so you just
Code:
stop
cp /system/framework/framework-res.old /system/framework/framework-res.apk
sync
start
and it will come back up without having to reformat or anything.
If it's bootlooping even when you use the adb method to copy, then your XMLs must be reencoding incorrectly. Post a list of all XMLs you have changed.
msticninja said:
Do not sign frameworks! How many time do I have to say this! System apps do not get signed...
Now, as far as the framework, there's two things to check. First, what XMLs have you edited? Second, instead of using root explorer to copy the framework, connect to a pc and use adb to perform these commands:
Code:
su
stop
cp /system/framework/framework-res.apk /system/framework/framework-res.old
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk
sync
start
If it continues boot-looping, you will still be connected through adb, so you just
Code:
stop
cp /system/framework/framework-res.old /system/framework/framework-res.apk
sync
start
and it will come back up without having to reformat or anything.
If it's bootlooping even when you use the adb method to copy, then your XMLs must be reencoding incorrectly. Post a list of all XMLs you have changed.
Click to expand...
Click to collapse
I do have my system set up for adb, but for some reason it don't read my A101, it works fine for my phone. The device manager shows my A101 listed as a Gen8 ADB Device, but it don't show up when i use the command: adb devices.
With your help I did manage to replace all of the stock .png's. I also found that I don't need to edit the .xml files to do what I want to. Thanks, for so much of your help! Although I would like to replace the .9.png's also and I understand that you must de-compile the .apk in order to do so. this way I could build a custom theme.
Rockstar52 said:
I do have my system set up for adb, but for some reason it don't read my A101, it works fine for my phone. The device manager shows my A101 listed as a Gen8 ADB Device, but it don't show up when i use the command: adb devices.
With your help I did manage to replace all of the stock .png's. I also found that I don't need to edit the .xml files to do what I want to. Thanks, for so much of your help! Although I would like to replace the .9.png's also and I understand that you must de-compile the .apk in order to do so. this way I could build a custom theme.
Click to expand...
Click to collapse
Have you done this yet(from the archos support site):
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
And disabled/reenabled debugging on the tablet?
msticninja said:
Have you done this yet(from the archos support site):
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
And disabled/reenabled debugging on the tablet?
Click to expand...
Click to collapse
No but I will give it a try and report back.
None of my changes are taking effect??!
Still not working, just a question. I am running Win7 64bit could this be the problem?? Do I need to be on a 32bit system to do the decompiling, compiling?
Tried on my wife's 32bit system still the same. For some reason it's not compiling the .apk right.
Rockstar52 said:
I am trying to create a custom theme, by modifying the framework-res.apk. I have been successful in porting some really cool .png files, but my problems start with the de-compiling & recompiling the .apk so I can modify the .xml & .9.png files. It seems every time I recompile my .apk it sends me in to a boot loop. I have used both APKTool and APK Manager with no luck. Here are my steps:
APK Manager:
1. Use a root explorer to copy the framework-res.apk.
2. Paste the file on my sd card.
3. Copy the file and paste it in the "place-apk-here-for-modding" folder.
4. Choose option 9 for compile.
5. Open the .xml file with Notepad++.
6. Recompile .apk using option 11.
7. Yes to "is this a system file?"
8. Yes to "keep original files & signatures"
9. Delete the files I modified from the "keep" folder and the resources.ascr file.
10. Finish the build of the .apk.
11. Copy & paste the modified .apk back to my sd card.
12. Rename the file from unsigned-framework-res.apk to framework-res.apk.
13. Use root explorer to cut & paste the modified to my /system/framework folder.
14. Reboot.
I now end up in a boot loop what am I doing wrong??
Click to expand...
Click to collapse
With ApkManager did you delete the 'public.xml' folder in ..\res\values ?
waterpolo said:
With ApkManager did you delete the 'public.xml' folder in ..\res\values ?
Click to expand...
Click to collapse
No, I did not. Was I supposed to?
EDIT: Ok I did some digging and what I have found is that the file size of the original framework-res.apk is 9.32mb. Once I rebuild it whether I modified anything or not the rebuilt .apk is only 7.34mb. Upon further inspection it seems to leave out all of the "value" named folders from the newly built .apk, and it does this whether I use APKTool or APK Manager(even though I say keep files). Has anyone else had this problem?
IM having the same problem,no solution though ! i edited bools.xml but after recompiling its not there ! Anyone solution ?

[TOOL][LINUX]ROMzilla - Batch ROM Decompile/Deodex/Build .apk and .jars! (8/1/12)

Here is ROMzilla Version 0.2.
http://d-h.st/pkp
First and foremost, I have fixed the issue with it not rebuilding files properly. Everything should go exactly where it's supposed to now.
The other modifications are numerous and subtle.
It will now deodex any odexed .zip you throw at it.
Included checking in numerous places for nonexistent files, folders, etc.
Merged routines for .jars and .apks.
You're now presented with one of three extraction options. Full, Custom, or Boot. Full will scan for all files in /app and /framework folders, and gut them into their respective folders in /edits.
Custom will extract anything you list in /scripts/custommod.txt. Be sure to include the full path from /system/. Ex: /system/app/FooApp.apk
Boot won't do anything for now. The line is commented out. I have the extraction down, but rebuilding needs some love yet.
For compiling, if existing /modded folder exists from previous compile, you will be prompted to backup. Files will be overwritten otherwise.
You will then be asked if you want to compile Full, Custom, or Boot.
Full will rebuild all folders found inside edits/system/framework and edits/system/app.
Custom will rebuild all folders specified in /scripts/custommod.txt.
Boot won't do squat right now.
Changes:
Added checking for existing /edits and/or /modded folders. Presents option to back up and then remove folders for clean extractions/rebuilds.
Added checking for existing working dir - skips .zip extraction if working dir found.
Created /in folder as location to look for .zip files to extract.
Renamed primary output folder to /extracted.
That's it for now.
http://d-h.st/pkp
Usage:
./ROMzilla.sh -d ROMNAME.zip
./ROMzilla.sh -d ROMFOLDERNAME
-Decompile ROM
./ROMzilla.sh -b ROMFOLDERNAME
-Compile files in -b
Reserved?
Thanks and rated! Very interesting!
Subscribed!
Sent from my PG86100 using Tapatalk 2
Interesting and suscribed, need a powerful automated script for ics/jb, thanks man.
Tested, works good, except for building and add folder res, resources.asrc into final apk, the script inject the entire folder into apk (/home/blabla/edits/rom/xxx.apk/res)
CLASS WORK DEV.
i have a small question
can i use this tool to cook rom of my huawei ideos x6?
what changes do i need to do?
Credits
Thanks Man
I'm just Learning to be a Developer
This will Help a Lot
All Credits in future will go to you :laugh::good::good:
Nice Work!!!!!!!
I am not from a linux background so I would like ask some to make it for the Windows. I'll be waiting.
Thanks:xgr7078
Hey guys, sorry, yes, I realized yesterday that the rebuild function was inserting full folders into the target files. I'm working on updating my device's root OTA file today, but when I get a chance, I will update the script. If someone else would like to do so in the meantime, you're more than welcome to.
Okay, updated OP with new/fixed version. Bunch of additions...
Thanks man
Enviado desde mi Galaxy Nexus
In the new version, folder tools not included. Add tools folder from first version and works great, in 0.2 add resources works like a charm, thanks for your work.
stenka85 said:
In the new version, folder tools not included. Add tools folder from first version and works great, in 0.2 add resources works like a charm, thanks for your work.
Click to expand...
Click to collapse
Er... could someone upload the tools folder?
jcejohnson said:
Er... could someone upload the tools folder?
Click to expand...
Click to collapse
there is no link for the original ROMzilla and without the /tools folder nothing works. could we get this fixed please????
Here is the tools folder.
tools.zip
af974 said:
Here is the tools folder.
tools.zip
Click to expand...
Click to collapse
thank you sir,
i am new to odex, when i execute this command in terminal, i have the following erros, it just can not handle the apks in /app, can you point me out to the right direction?
ROMzilla.sh -d miui_NS_2.8.10 (miui_NS_2.8.10 is my ROM.zip file)
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "out"
at org.jf.smali.main.main(main.java:184)
mv: 无法获取"out.dex" 的文件状态(stat): 没有那个文件或目录
rm: 无法删除"out": 没有那个文件或目录
rm: 无法删除"classes.dex": 没有那个文件或目录
##################################
Decompiling XiaomiServiceFramework.odex...
##################################
Can't find the file XiaomiServiceFramework.odex
rm: 无法删除"XiaomiServiceFramework.odex": 没有那个文件或目录
Recompiling.
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "out"
at org.jf.smali.main.main(main.java:184)
mv: 无法获取"out.dex" 的文件状态(stat): 没有那个文件或目录
rm: 无法删除"out": 没有那个文件或目录
rm: 无法删除"classes.dex": 没有那个文件或目录
What would you like to extract?
so what is the problem? thanks in advanced?
chshrm said:
thank you sir,
i am new to odex, when i execute this command in terminal, i have the following erros, it just can not handle the apks in /app, can you point me out to the right direction?
ROMzilla.sh -d miui_NS_2.8.10 (miui_NS_2.8.10 is my ROM.zip file)
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "out"
at org.jf.smali.main.main(main.java:184)
mv: 无法获取"out.dex" 的文件状态(stat): 没有那个文件或目录
rm: 无法删除"out": 没有那个文件或目录
rm: 无法删除"classes.dex": 没有那个文件或目录
##################################
Decompiling XiaomiServiceFramework.odex...
##################################
Can't find the file XiaomiServiceFramework.odex
rm: 无法删除"XiaomiServiceFramework.odex": 没有那个文件或目录
Recompiling.
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "out"
at org.jf.smali.main.main(main.java:184)
mv: 无法获取"out.dex" 的文件状态(stat): 没有那个文件或目录
rm: 无法删除"out": 没有那个文件或目录
rm: 无法删除"classes.dex": 没有那个文件或目录
What would you like to extract?
so what is the problem? thanks in advanced?
Click to expand...
Click to collapse
Well i'm not this app developer but i'll try to help you:
Your Rom_Name.zip must be in the folder named "in"
from terminal :
Code:
./ROMzilla.sh -d Rom_Name.zip
You need a Linux distro though or Cygwin under Windows.
thanks a lot for your quick reply, sir. yes i did use this tool in linux system, and i did put the rom in the folder "in", btw, my rom is base on ICS 4.0.4.
Thank you for your work!!!! It works great!

help me how to install

my rom is stock odex i used universal deodexer and deodexed my.system/app and system/framework folders in my pc . now my question.how can i install that app and framework folders to my phone ??(i tried replace with root explorer but it does not .(how can i make thats to a flashable zip?
but
my problem is not that . i can make a flashable zip . its working fine but after i flashed old .odex files doesnt delete. how can i add it to meta inf for when flashing delete app and replace new app and same for framework
You just need to put in a simple delete line into the update script
for example
Code:
delete("/system/app/Vending.apk");
will delete the Vending.apk from the folder system/app
remember if you are manually pushing files with a root browser you need root permissions and you need to set the correct file permissions - for most apps in the app folder it will be rw-r-r
thnx
thanx i learned if i want to delete folde i will use delete_recursive
help
look .
delete(system app systemui.odex
this is working succesfully but after i flashed my zip system ui is lost . it doesnt show . i looked system app its deodexed permissions is rw--r-r its true but doesnt show . what's can i do ?
denizarca said:
look .
delete(system app systemui.odex
this is working succesfully but after i flashed my zip system ui is lost . it doesnt show . i looked system app its deodexed permissions is rw--r-r its true but doesnt show . what's can i do ?
Click to expand...
Click to collapse
most likely if the status bar just doesn't show but does not display a force closed message its because the SystemUI.apk is not correctly signed
as long as the file name is correct and it is correctly compiled with no errors the only thing left is the signing
You can sign an apk easily with zipsigner (playstore)
just copy the apk to any folder on your sd card
start zip signer
select your apk as the input
select the name you want to call it for the output (make it different from the input - you can change the name later)
select platform key as the key you wish to sign (this is for system apps for user apps use a test key)
sign the apk
once done the apk will be outputted as a zip file
change the name of this zip to the name of your apk and don't forget to change the .zip extension back to .apk
put in a flashable and flash in cwm with system mounted
you can check any errors with the SystemUI.apk by doing a logcat via adb as the phone is starting up
By searching the logcat for SystemUI you will be able to see any errors in it and why its not starting - eg Signature mismatch skipping loading

How to Deodex Lollipop 5.1.1 (10.7.A.0.222)

Hey guys! Since deodexing older Z series phones with this latest update has been a pain in the *** for deodexing here's a detailed guide on how to get a correctly deodexed system folder and avoid bootloops...
First part: Getting files from the phone.
To get the files from our phone first we'll have to install ADB Drivers, you can find them here on xda or go google it. Once you have adb drivers installed go to the folder where you installed them. Press Shift while right clicking on the folder and select Open command promp.
Here are the commands to get the folders with apk, note that you'll find them in your C:\ folder.
- To get app folder:
Code:
adb pull /system/app /app/
- To get framework folder:
Code:
adb pull /system/framework /framework/
- To get priv-app folder:
Code:
adb pull /system/priv-app /priv-app/
You will get apk's only on app and priv-app folders, the only folder with odex files (arm folder) will be framework.
------------------------------------------------------------------------------------------------------------
Now let's go for sqsh files to get odex files for app and priv-app folders.
- To get odex.app.sqsh:
Code:
adb pull /system/odex.app.sqsh
- To get odex.app.sqsh:
Code:
adb pull /system/odex.priv-app.sqsh
You'll find these files inside the same folder where adb.exe is
Second part: Unpacking .SQSH files
To resume a little, you may refer to IaguCool's guide
Once you have downloaded SquashFS Tool, move both .sqsh files to the folder.
When you have opened the command promp use these codes to extract files...
> To get odex files for app folder (After extracting rename the squash-root folder to app):
Code:
unsquashfs -no-xattrs odex.app.sqsh
> To get odex files for priv-app folder (After extracting rename the squash-root folder to priv-app):
Code:
unsquashfs -no-xattrs odex.priv-app.sqsh
Third part: Merging files
Create a folder named system and move app, framework and priv-app folders from C:\ to the new folder.
After that grab the folders you extracted with SquashFS Tool and merge them with app and priv-app folder.
After doing this move SemcGenericUxpRes folder to priv-app folder
Fourth part: Deodexing
Download JoelDroid's Lollipop Batch Deodexer and replace the file named oat2dex.jar found on /tool folder with this one: Latest oat2dex
Then open the program and select the /system/ you've created to start the process.
Once it has finished, grab SemcGenericUxpRes folder and move it back to /framework
Now you can either replace folders manually on your phone using TWRP by moving the deodexed system folder to your phone and mounting System partition, erasing app, framework and priv-app folder and then pasting the ones from the deodexed folder. OR make a flasheable zip.
How to manually move folders to /system partition
> Boot to recovery (TWRP MANDATORY)
> Mount system partition
> Go to file manager and go to: /system/ partition
> Manually delete app, framework and priv-app folder (you must first open the folder, then open the menu and delete)
> Then go to where you put the deodexed folders, open app folder, open menu, choose copy and paste on /system/ folder, same process for priv-app and framework.
> Once you're done go to Wipe option, choose advanced wipe and wipe Dalvik-cache and cache.
> Boot and you're good to go! No need to fix permissions
In both cases, after you have either flashed or replaced the folders, go to Wipe option > Advanced Wipe and clean Dalvik-cache and cache to avoid problems.
Does it have issue with OpenGL and Play Store?
Sent from my D6503 using Tapatalk
RyTekk said:
Does it have issue with OpenGL and Play Store?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
No, that's why you need to download latest oat2dex version See deodexing part
Why not just copy App, priv-app and framework folder from system and deodex them?
Black_Eyes said:
Why not just copy App, priv-app and framework folder from system and deodex them?
Click to expand...
Click to collapse
Cause you get bootloop if you just replace odex files present in app and priv-app (Especially after replacing the deodexed framework folder in system).
If you extract via adb you'll get app and priv-app folders clean, without odex files. That way you can make a cleaner deodex since you don't replace .odex files, just merge both folders in one, app with .apks and app with .odex
I wish it was as easy as in 5.0.2 but no, on 5.1.1 is way more complicated to have a properly deodexed system.
BTW i've tried by deodexing manually by copying folder and then boot into recovery delete app, priv-app and framework folder via TWRP file manager and then flashed the deodexed zip and it worked
C:\adb>adb pull /system/odex.app.sqsh
remote object '/system/odex.app.sqsh' does not exist
C:\adb>adb pull /system/odex.priv-app.sqsh
remote object '/system/odex.priv-app.sqsh' does not exist
help
Everything was fine except google play services, it crashes every time i want add account
Perfect work @xkeita ,
I saw you asking so many guys about deodexing .222 firmware these days and finally you managed!
Great work, great tutorial. I will try asap.
could you provide the zip? or the zip from this thread http://forum.xda-developers.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596 can be used?
zyclops1 said:
C:\adb>adb pull /system/odex.app.sqsh
remote object '/system/odex.app.sqsh' does not exist
C:\adb>adb pull /system/odex.priv-app.sqsh
remote object '/system/odex.priv-app.sqsh' does not exist
help
Click to expand...
Click to collapse
same problem..
edi194 said:
Everything was fine except google play services, it crashes every time i want add account
Click to expand...
Click to collapse
Same here bro
I thought I had accidently deleted some necessary google services files while removing bloatwares so I tried flashing latest Gapps for 5.1.1 over stock sony FW but no effect. Can't figure out why
I'm having Xperia ZR (5.1.1 Stock)
zyclops1 said:
C:\adb>adb pull /system/odex.app.sqsh
remote object '/system/odex.app.sqsh' does not exist
C:\adb>adb pull /system/odex.priv-app.sqsh
remote object '/system/odex.priv-app.sqsh' does not exist
help
Click to expand...
Click to collapse
gundam_warlock said:
could you provide the zip? or the zip from this thread http://forum.xda-developers.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596 can be used?
same problem..
Click to expand...
Click to collapse
If you have an Xperia Z1 it might differ from this a little bit, I think those don't have odex.xx.sqsh on their filesystem, check if you have odex files in app and priv-app.
Phones that I know that so far work with this sqsh filesystem are Xperia Z, ZL, ZR, Xperia Tablet Z
edi194 said:
Everything was fine except google play services, it crashes every time i want add account
Click to expand...
Click to collapse
sshivampp said:
Same here bro
I thought I had accidently deleted some necessary google services files while removing bloatwares so I tried flashing latest Gapps for 5.1.1 over stock sony FW but no effect. Can't figure out why
I'm having Xperia ZR (5.1.1 Stock)
Click to expand...
Click to collapse
Did you clear dalvik-cache and cache? If it still gives you googleplayservices fc, manually download the GooglePlayServices from APKMirror and install as normal app
xkeita said:
If you have an Xperia Z1 it might differ from this a little bit, I think those don't have odex.xx.sqsh on their filesystem, check if you have odex files in app and priv-app.
Phones that I know that so far work with this sqsh filesystem are Xperia Z, ZL, ZR, Xperia Tablet Z
Click to expand...
Click to collapse
I tried to deodex directly without pull sqsh, everything except nfcnci failed, when i tried to copy to system and reboot, nfc is fc. When check nfcnci folder only apk and lib folder exsist, but nothing exsist inside lib folder.
Where do i wrong?
xkeita said:
Did you clear dalvik-cache and cache? If it still gives you googleplayservices fc, manually download the GooglePlayServices from APKMirror and install as normal app
Click to expand...
Click to collapse
Dalvik-cache & Cache ! I tried wiping the whole data, it didn't work.
App install window goes on forever and app not installing.
Got it working by installing latest play services before deodexing. (as the updated play services app in the data partition runs, no matter if system is having broken play services package)
Fixed it for now but still wondering what causes the issue
sshivampp said:
Fixed it for now but still wondering what causes the issue
Click to expand...
Click to collapse
same issue here , how can i fix this?
@xkeita Bro if not ask for much could create a video tutorial ? ?????
Hamidreza2010 said:
same issue here , how can i fix this?
Click to expand...
Click to collapse
what I did is flashed the ftf (to go back to stock)
installed latest play services via play store
then followed the deodexing guide
Note: after deodexing, do not wipe data or uninstall updated play services otherwise error will occur again
works fine thank you
ZR 5.1.1
After download the rom by XperiaFirm I must continue this step?
Second part: Unpacking .SQSH files
To resume a little, you may refer to IaguCool's guide
Once you have downloaded SquashFS Tool, move both .sqsh files to the folder.
When you have opened the command promp use these codes to extract files...
> To get odex files for app folder (After extracting rename the squash-root folder to app):
Code:
unsquashfs -no-xattrs odex.app.sqsh
> To get odex files for priv-app folder (After extracting rename the squash-root folder to priv-app):
Code:
unsquashfs -no-xattrs odex.priv-app.sqsh
Third part: Merging files
Create a folder named system and move app, framework and priv-app folders from C:\ to the new folder.
After that grab the folders you extracted with SquashFS Tool and merge them with app and priv-app folder.
After doing this move SemcGenericUxpRes folder to priv-app folder
Fourth part: Deodexing
Download JoelDroid's Lollipop Batch Deodexer and replace the file named oat2dex.jar found on /tool folder with this one: Latest oat2dex
Then open the program and select the /system/ you've created to start the process.
Once it has finished, grab SemcGenericUxpRes folder and move it back to /framework

Categories

Resources