Update 15.02.2015:
- Works also with official Kitkat Update from Kingzone (4.4.2)...
- Step 1,2 deleted, as Unreal Deodexer doesnt need JDK and SDK. (i worked with other deodexer tools before which needed JDK + SDK...). Thanks to Eben80 and other guys for the hints....
- Step 4+5 corrected and added by some better command lines from Eben80. (Cheers!)
.... and finally some additional comments due to questions:
a) I'm not very busy on XDA, so please be patient with low support from my side...
b) i cannot upload any video tutorials nor any complete ROMS as my connection bandwith allows no big upload files nor do i want to as i normally work 12h/day and have some other duties as well....
... thx for understandig..... ...
Update 15.02.2015:
_________________________________________________________________________
Hi Folks,
i just wanted to give my experience with my new Kingzone K1 Turbo which is running with a MediaTek MT6592 processor.
I experienced bootloops before going deeper into the forums and the web and it took me 4-5 days to solve the problem.
The main problem was to find a deodexer tool to deodex the apks and the framework files for the stock rom (i was eager to run it on the rooted stock rom as it provides support for the QI Wireless Charger Flip Cover and Air Gestures)
Here is my solution which worked very good and easy (after 5 days of finding the right deodex tool!). I used a WinXP computer with the rooted phone via USB connected.
Preconditions:
rooted phone, USB Debugging enabled on phone, ADB available on your connected WINDOWS computer.
1.) o b s o l e t e - deleted on 15.02.2015
2.) o b s o l e t e - deleted on 15.02.2015
3.) Use a specially modified Tool Chain with adjusted smali/baksmali for the MTK MT6592 / Alyiun OS called "Ureal-Deodexer". See https://code.google.com/p/smali/issues/detail?id=199 (use DL-Link in Post#16)
4.) after deodexing apks and framework put new deodexed files from app + framework folder of Unreal-Deodexer on your SD Card on the phone in following folders :
/done_app
/done_framework
5) after having copied app + framework folder contents from unreal deodexer tool to /done_app and /done_framework on your phones sdcard open a command prompt window in windows with the phone connected via USB and enter following command lines:
Code:
adb remount
adb shell
stop
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
rm /system/app/*.jex
cp /sdcard/done_framework/* /system/framework/
rm /system/framework/*.odex
rm /system/framework/*.jex
echo dalvik.vm.execution-mode=int:fast >> /system/build.prop
reboot recovery
5a.) Now phone should be in Recovery mode.
Wipe cache + dalvik cache in recovery. (Important to delete both caches! Otherwise phone might be stuck @ reboot...)
6.) reboot the phone (now deodexed rom needs quite a while for the first startup....)
7.) JJJJJJJJJJJJJJJIIIIIIIIIIIIIIIPPPPPPPPPPPPPPEEEEEEEEEEEEEEEEEE.......
8.) now i was able to install Xposed Framework and all my favorite Xposed modules.
Now my Kingzone K1 Turbo runs like hell and much faster than before. And the best: With Xposed Framework and all downloaded modules (e.g. Gravity Box) fully working.
I think this will also help with other phones with a MTK MT6592 / Aliyun OS but of course i cannot guarantee as i could not test on other phones.
Try on your own risk.....
Cheers,
Superstone
superstone said:
Hi Folks,
i just wanted to give my experience with my new Kingzone K1 Turbo which is running with a MediaTek MT6592 processor.
I experienced bootloops before going deeper into the forums and the web and it took me 4-5 days to solve the problem.
The main problem was to find a deodexer tool to deodex the apks and the framework files for the stock rom (i was eager to run it on the rooted stock rom as it provides support for the QI Wireless Charger Flip Cover and Air Gestures)
Here is my solution which worked very good and easy (after 5 days of finding the right deodex tool!). I used a WinXP computer with the rooted phone via USB connected.
1.) Install newest Java JDK on the computer and link the installation path with the Win system / user variables. (see http://forum.xda-developers.com/showthread.php?t=2374008 Post#9)
2.) Install Android SDK. Be sure that the correct repositories for your Android Versions are also installed. If not install (e.g. for my Android 4.2.2. Version i needed all API 17 resources...)
3.) Use a specially modified Tool Chain with adjusted smali/baksmali for the MTK MT6592 / Alyiun OS called "Ureal-Deodexer". See https://code.google.com/p/smali/issues/detail?id=199 (use DL-Link in Post#16)
4.) after deodexing apks and framework put it onto the phone via Android.SDK. (see e.g. http://forum.xda-developers.com/showthread.php?t=2374008 Post#1 how to do this)
5.) after that modify /system/build.prop by adding a line with
Code:
dalvik.vm.execution-mode=int:fast
.
6.) reboot the phone (now deodexed rom needs quite a while for the first startup....)
7.) be sure that all .jex files and .odex files are removed from /system/app and /system/framework. (i did it with a file explorer with root access for /system directly on the phone) Reebot again in case you have to delete.
8.) now i was able to install Xposed Framework and all my favorite Xposed modules.
Now my Kingzone K1 Turbo runs like hell and much faster than before. And the best: With Xposed Framework and all downloaded modules (e.g. Gravity Box) fully working.
I think this will also help with other phones with a MTK MT6592 / Aliyun OS but of course i cannot guarantee as i could not test on other phones.
Try on your own risk.....
Cheers,
Superstone
Click to expand...
Click to collapse
Can you backup your rom with mtkdroidtools and share it on needrom.com, it will be nice for people who want a stock rom with xposed working.
Sorry to say, but my current upload bandwith to upload a whole rom would take me hours as i have a very rural ADSL connection.
I processed these steps now also with another phone (a doogee dg550 -also with a MTK MT 6592) within family and it also worked. Took me about 1 hours there with all tools allready installed on PC.
Deoxeding with the ureal deodexer is just a one click process.
U just need a bit to download and to integrate JDK and Android SDK on your PC.
Sent from my K1 turbo using XDA Free mobile app
superstone said:
Hi Folks,
i just wanted to give my experience with my new Kingzone K1 Turbo which is running with a MediaTek MT6592 processor.
I experienced bootloops before going deeper into the forums and the web and it took me 4-5 days to solve the problem.
The main problem was to find a deodexer tool to deodex the apks and the framework files for the stock rom (i was eager to run it on the rooted stock rom as it provides support for the QI Wireless Charger Flip Cover and Air Gestures)
Here is my solution which worked very good and easy (after 5 days of finding the right deodex tool!). I used a WinXP computer with the rooted phone via USB connected.
1.) Install newest Java JDK on the computer and link the installation path with the Win system / user variables. (see http://forum.xda-developers.com/showthread.php?t=2374008 Post#9)
2.) Install Android SDK. Be sure that the correct repositories for your Android Versions are also installed. If not install (e.g. for my Android 4.2.2. Version i needed all API 17 resources...)
3.) Use a specially modified Tool Chain with adjusted smali/baksmali for the MTK MT6592 / Alyiun OS called "Ureal-Deodexer". See https://code.google.com/p/smali/issues/detail?id=199 (use DL-Link in Post#16)
4.) after deodexing apks and framework put it onto the phone via Android.SDK. (see e.g. http://forum.xda-developers.com/showthread.php?t=2374008 Post#1 how to do this)
5.) after that modify /system/build.prop by adding a line with
Code:
dalvik.vm.execution-mode=int:fast
.
6.) reboot the phone (now deodexed rom needs quite a while for the first startup....)
7.) be sure that all .jex files and .odex files are removed from /system/app and /system/framework. (i did it with a file explorer with root access for /system directly on the phone) Reebot again in case you have to delete.
8.) now i was able to install Xposed Framework and all my favorite Xposed modules.
Now my Kingzone K1 Turbo runs like hell and much faster than before. And the best: With Xposed Framework and all downloaded modules (e.g. Gravity Box) fully working.
I think this will also help with other phones with a MTK MT6592 / Aliyun OS but of course i cannot guarantee as i could not test on other phones.
Try on your own risk.....
Cheers,
Superstone
Click to expand...
Click to collapse
Hi,
thank you for shareing your solution. I just tryed it and it seems to work fine. One question left for me, what about the *.jex files frome the /system/framework/ folder? Have you removed them?
kind regards
Joern
Yes. I have removed ALL .jex files after deodexing, putting all files on the phone in /system/app and /system/framework and the first reboot afterwards. I think i also cleared the complete dalvik cache afterwards again. I cleared dalvik cache several times via TWRP recovery.
One thing i have discovered with the doogee dg550,but this is really the only thing. Everything else works like a charm:
After all these steps performed there is a force close when i go to system settings/display (e.g. for changing the display timeout until lockscreen). Its not a killer because i can also change relevant settings via gravity box.
Anybody has any idea why?
With the kingzone k1 turbo phone dont have this problem. Absolutely no problem here.
Sent from my K1 turbo using XDA Free mobile app
superstone said:
Yes. I have removed ALL .jex files after deodexing, putting all files on the phone in /system/app and /system/framework and the first reboot afterwards. I think i also cleared the complete dalvik cache afterwards again. I cleared dalvik cache several times via TWRP recovery.
One thing i have discovered with the doogee dg550,but this is really the only thing. Everything else works like a charm:
After all these steps performed there is a force close when i go to system settings/display (e.g. for changing the display timeout until lockscreen). Its not a killer because i can also change relevant settings via gravity box.
Anybody has any idea why?
With the kingzone k1 turbo phone dont have this problem. Absolutely no problem here.
Sent from my K1 turbo using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you removed all the *.jar.jex files after deodexing? Most of the *.jar.jex files are bigger then their *.jar files! Changing Display settings is working without problems with my Kingzone K1 turbo. Xposed Framework and GravityBox JB are also working with no problems :good:
---------- Post added at 08:50 AM ---------- Previous post was at 08:13 AM ----------
the *.jar.jex files are only in the Framework folder. You have to remove them one by one on your rooted phone or you have to remove them with ADB and the "rm" command.
4.) after deodexing apks and framework put it onto the phone via Android.SDK. (see e.g. http://forum.xda-developers.com/show....php?t=2374008 Post#1 how to do this)
Click to expand...
Click to collapse
This step was not mentioned in this link, so I guess you still have the jex files still in your Frameworks folder. This is no problem if they have to stay there, I just want to know.
I can confirm that i removed all .jex files in the /system/framework folder after the first phone reboot with deodexed files in /system/app and /system/framework. (More or less Step No.7)
That means i pushed all deodexed files via adb on the phone (including .jex). Rebooted. And afterwards deleted all .jex files with x-plore (a file Explorer available in play store) which i habe given root access in the settings (is a must. Otherwise the file Explorer on the phone wont habe access to /system folder)
ATTENTION: DO NOT REMOVE THE .JAR FILES IN /SYSTEM/FRAMEWORK after pushing deodexed files in system folder!!!
Sent from my K1 turbo using XDA Free mobile app
JRapsky said:
Are you sure you removed all the *.jar.jex files after deodexing? Most of the *.jar.jex files are bigger then their *.jar files! Changing Display settings is working without problems with my Kingzone K1 turbo. Xposed Framework and GravityBox JB are also working with no problems :good:
---------- Post added at 08:50 AM ---------- Previous post was at 08:13 AM ----------
the *.jar.jex files are only in the Framework folder. You have to remove them one by one on your rooted phone or you have to remove them with ADB and the "rm" command.
This step was not mentioned in this link, so I guess you still have the jex files still in your Frameworks folder. This is no problem if they have to stay there, I just want to know.
Click to expand...
Click to collapse
ATTENTION: TO AVOID ANY MISSUNDERSTANDING. DO NOT REMOVE THE .JAR FILES after pushing deodex files in system!!!
Only remove .jex files in /system/framework via ADB rm command or via a root access given file Explorer on the phone.
Sent from my K1 turbo using XDA Free mobile app
I have a problem using the unreal deodexer. It stops pulling the framework whenever framework.jar is already pulled. So I manually placed the framework files and apps in the folder. The next problem is when deodexing the files. It keeps saying that "System\app not found"
How do I fix it?
---------- Post added at 02:42 PM ---------- Previous post was at 02:07 PM ----------
nvm. i got it working now. I downloaded the unreal deodexer from your link. Solution to path not found was in the instructions. There should be no spaces in the path.
when I move deodexed apps
Code:
cp /storage/sdcard0/done_app/* /system/app/
I get lots of errors. Many apks are listed, with the error either 'Invalid argument' or 'No space left on device'. there is plenty of space left on device.
Phone hangs at boot
I followed all previous steps, with no other issues occurring.
Does anyone know what I should do?
Phone is Jiau G6, also running Aliyun OS
Thanks.
update:
In the op it states to move deodexed files to device via android.sdk
I just tried it via a flashable zip, and after deleting .jex and .odex, phone was stuck in boot again.
Are files really deodexed sucessfully on pc? Any folder (including all subfolders) with a empty space in the name?
Do you have root access to your phone? Check if you are able to Copy any other file via ADB shell (maybe a simple txt file) to your /system folder. If not root access is missing.
Any error message while entering the 'su' command via ADB shell? Is USB debugging enabled on the phone? Are your apks really on sdcard0 or maybe in sdcard1? Check in ADB shell with
cd /storage/sdcard0
ls
If files are really there.
If not change the source folder in CP command.
Sent from my K1 turbo using XDA Free mobile app
jaw2floor said:
update:
In the op it states to move deodexed files to device via android.sdk
I just tried it via a flashable zip, and after deleting .jex and .odex, phone was stuck in boot again.
Click to expand...
Click to collapse
Have you modified your built.prop with the additional command line before deleting .odex and .jex files?
Code:
dalvik.vm.execution-mode=int:fast
Which Android version do you have?
Is Xposed Framework already installed @ your stuck reboot?
If it reboots again completely by repeatingly shortly pressing a volume key @ startup (4 times pressing a button in startup sequence stops xposed framework to start - promted by a vibration or tone) then your should remove xpossed framework and reebot again and check if you are really running completely deodexed. and install xposed again.
Maybe a dalvik cache wipe via recovery would also help. (i did that also several times)
Cheers,
Superstone.
superstone said:
Are files really deodexed sucessfully on pc? Any folder (including all subfolders) with a empty space in the name?
Do you have root access to your phone? Check if you are able to Copy any other file via ADB shell (maybe a simple txt file) to your /system folder. If not root access is missing.
Any error message while entering the 'su' command via ADB shell? Is USB debugging enabled on the phone? Are your apks really on sdcard0 or maybe in sdcard1? Check in ADB shell with
cd /storage/sdcard0
ls
If files are really there.
If not change the source folder in CP command.
Sent from my K1 turbo using XDA Free mobile app
Click to expand...
Click to collapse
superstone said:
Have you modified your built.prop with the additional command line before deleting .odex and .jex files?
Code:
dalvik.vm.execution-mode=int:fast
Which Android version do you have?
Is Xposed Framework already installed @ your stuck reboot?
If it reboots again completely by repeatingly shortly pressing a volume key @ startup (4 times pressing a button in startup sequence stops xposed framework to start - promted by a vibration or tone) then your should remove xpossed framework and reebot again and check if you are really running completely deodexed. and install xposed again.
Maybe a dalvik cache wipe via recovery would also help. (i did that also several times)
Cheers,
Superstone.
Click to expand...
Click to collapse
I think i may have forgot to add the build.prop when i tried the second time, using the .zip method. I defo have root and the folder locations are correct etc. I will try the whole procedure again tomorrow.
Is there a reason you mention in the OP to push deodexed files by android.sdk and not by .zip?
Android version is 4.2.2 and xposed was not already installed.
Thanks,
You should modify your build.prop by adding the command line (i added it just after other dalvik command lines) before your first reboot without .jex files.
I prefered the ADB Methode to copy deodexed files from SD card to system folder because while stopping the system via ADB you still can check by cd + ls commands if files are really copied in the relevant folders and do a manual reboot after check..
Sent from my K1 turbo using XDA Free mobile app
Tried again on a different computer, d'loaded all files again. Still got errors in pushing deodexed files, then phone hangs at boot.
Here's the errors im getting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I complete the other commands still, and they dont give any errors
Hmmm.
Looking at the Screenshot i assume that all files up to quicksearchbox.apk are copied and from the beginning of quicksearchbox u have a problem right?
It seems that u have no space left on the root folder also right?
a) check manually if all files are correctly available in /scdard/done_app before pushing into /system/APP by cp command and if all are bigger than 0kB by
cd /sdcard/done_app
ls
If not u try to copy from a folder which is not available. Some phones have differences in the real scard folder. Some phones need /sdcard0 or /scdard1 depending on mount config from Rom.
Check by cd + ls commands if source folder is correct and if destination folder is ok.
Regarding disk space. How much space is left in /root?
Do u use a newly flashed Rom? Did u perform a full wipe via recovery before procedure?
Sent from my K1 turbo using XDA Free mobile app
Worked on my Ubtel Q1 octacore mtk6592 thx
hey guys.
i got some trouble with deodexing the stock rom of my zopo zp980+. i have no idea what the problem is. there are no issues while the whole procedere. but when i try to reboot the phone after deodexing the app and framework files and replacing theme with adb, it stucks on the bootscreen.
i am not sure, but maybe there are problems with the .odex files. as i tried it with flashing the deodexed files with the sample-file it worked. but after deleting .odex and .jar.jex files and rebooting the phone, it again stucks at the bootscreen.
has anybody expirience by deodexing zopo-roms? or an idea, because of what i get these issues?
i hope you understand what i'm trying to tell you - the years in school with english-lessons are a long time ago.
I understand that phone freezes after you copied files sucessfully from sdcard to /system folder during the reeboot afterward, Right?
Did you modify your built.prop like described before the reebot after copy files to /system?
If yes try to wipe dalvik cache.
On the first reebot after putting deodexed files in system and modifying built.prop the phone can need a long time for first startup because it has to rebuilt dalvik cache.
Sent from my K1 turbo using XDA Free mobile app
i found on a russian the deodexed latest stock rom, so my problem is theoretically solved.
but i dont understand why it doesn't worked. i've tried to wipe dalvik and copy the files again but the phone freezes again at the bootscreen.
i've added the build.prop line
"dalvik.vm.execution-mode=int:fast"
Click to expand...
Click to collapse
before i deodexed the rom, but i tried to wiped the dalvik cache before rebooting.
the phone was freezing for 10 minutes after that, then i went back to recovery and flashed the russian deodexed rom.
Related
You will have to manually install it via adb push or adb shell.
Below is the link for a package that contains /system/app and /system/framework fully deodexed and zipaligned (not signed). It's the Stock version, I didn't remove any apk or framework.
Use at your own risk!
Backup your /system before upgrade!
I did notice speed increase and better memory utilization.
http://www.usk.bz/android/system-deodexed.bz2
EDIT: Here is a quick howto do it. Do some research, speacially on the "Recovering from a software brick" thread posted by Designgears. You may need it, in ase you don't execute this right.
Warning: Do those steps carefully! If you get any error as a return for a command you did, stop immediately and post here with the error to make sure it's safe to continue or what you should do before continue.
1. Download the file system-deodexed.bz2 (it's a tar.bz2)
2. uncompress it with tar zxf system-deodexed.bz2. You will get a folder called "system" with two other folders inside(app and framework).
3. First push it to the device to a safe location (your internal sdcard):
Code:
adb push system /mnt/sdcard/deodexed/system
4. Now open an adb shell and backup the folders you will mess with to the sd card, in case you need to recovery them
Code:
adb shell
$ su
# mkdir /mnt/sdcard/original_system
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework
# cp /system/app/* /mnt/sdcard/original_system/app
# cp /system/framework/* /mnt/sdcard/original_system/framework
5. Now the tricky part, you will get force closes on the device screen, because you will do this with the system running, don't worry for now. It should clear up once you are done. (Thx for the tip!) Lets update the system with the deodexed files. While still on the adb sheel as root, from the previous step, continue with these commands:
Code:
# stop
# mount -o rw,remount /dev/block/mmcblk0p12 /system
# cp /mnt/sdcard/deodexed/system/framework/* /system/framework
# cp /mnt/sdcard/deodexed/system/app/* /system/app
# rm /system/framework/*.odex
# rm /system/app/*.odex
6. Once you are done, exit the adb shell and do a reboot:
Code:
adb reboot
It should take a little longer to reboot, its normal for the first time. Then you should have normal boot speeds.
I recommend do this on a clear system, or that you do a factory reset once you reboot. The reason for that is that sometimes you get some data corruption during the force closes (corruption on the configuration files, not user data). But a factory reset fixes that.
If all go well, you have a deodexed system and are ready to use some Mods!
Have fun!
[ Known issues ]
- None! Please report if you notice anything!
http://forum.xda-developers.com/showthread.php?t=961382
Hey, here is a fully working on I did over the weekend.
Thanks! I didn't see it before. Will still compare with mine to see which package I messed up.
uskr said:
Thanks! I didn't see it before. Will still compare with mine to see which package I messed up.
Click to expand...
Click to collapse
usually packages with sound files get messed up for whatever reason when deodexing
designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Are you still planning on posting your mod version with steps? I am asking because I want to take look before making I own edits if necessary. I figured you may have it the way I want and it would less work for me either way.
designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Do you use an automated script to deodex them? or manually do one by one? The BOOTCLASSPATH dependencies sometimes give me some headache.
Also, do you mind to share which zip compression level do you use to repackage them?
Thank again!
designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Actually, I just tried yours and it has the same problem. Can you try to add the "Social Status" motorola widget to your MotoBlur and tap it to Setup your account and see if it starts something?
Mine doesnt start the Setup intent and I can see a Java exception on adb logcat.
uskr said:
Actually, I just tried yours and it has the same problem. Can you try to add the "Social Status" motorola widget to your MotoBlur and tap it to Setup your account and see if it starts something?
Mine doesnt start the Setup intent and I can see a Java exception on adb logcat.
Click to expand...
Click to collapse
Nevermind. Neither were bugged. I installed the deodexed without a data wipe and something got corrupted on the /data (some configuration file or something). I did a factory data reset and everything is working!
Not to play with changing some apks!
Hi guys,
I don't have an Atrix for now, so maybe it's just a dumb question. Sorry if it is.
With the Defy, if you push files and your phone won't reboot because you messed with something, you're screwed, as we don't have a true custom recovery. (you need a booting system to be able to get to the bootstap custom recovery, which you can't get into if your system is messed and the phone doesn't boot).
So when we are in that case with a Defy, our only option is to reflash a Motorola signed sbf file using RSD lite, root again, install again bootstrap recovery,... and try again ;-).
I guess it has to be the same with the Atrix (as the bootloader is locked as in the Defy)
So my question is:
- Are there already Atrix sbf files out there to recover a soft-bricked Atrix?
- If not, how do you recover it if you messed with the system files and the Atrix won't boot into a working system (of at least a state where you can get root shell though adb).
adlx.xda said:
So my question is:
- Are there already Atrix sbf files out there to recover a soft-bricked Atrix?
- If not, how do you recover it if you messed with the system files and the Atrix won't boot into a working system (of at least a state where you can get root shell though adb).
Click to expand...
Click to collapse
If you only messed only with /system/app or /system/framework folders/files, designgear posted how to recovery those files using the stock, that you can also download a tar with all the /system files from this forum.
Updated the post with a short howto.
If you get a software brick, search the forum for a post from designgears about how to recovery from a software brick.
As per the link below - I type "stop" once in the adb shell and it allowed me to transfer everything over without corrupting everything.
http://forum.androidcentral.com/mot...cks/30539-how-manually-deodex-your-phone.html
slhawkins said:
As per the link below - I type "stop" once in the adb shell and it allowed me to transfer everything over without corrupting everything.
http://forum.androidcentral.com/mot...cks/30539-how-manually-deodex-your-phone.html
Click to expand...
Click to collapse
Thx. Added to the howto!
uskr said:
Thx. Added to the howto!
Click to expand...
Click to collapse
Add the following to your instructions otherwise you will get an error message
You need the below line before the others
# mkdir /mnt/sdcard/original_system
The below are in your original instructions but the above is needed prior to the below
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework
lpsi2000 said:
Add the following to your instructions otherwise you will get an error message
You need the below line before the others
# mkdir /mnt/sdcard/original_system
The below are in your original instructions but the above is needed prior to the below
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework
Click to expand...
Click to collapse
Thanks! Updated.
I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?
NguyenHuu said:
I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?
Click to expand...
Click to collapse
Extract it to the file with no extension.
Open winrar.
Drag drop this file into that (u'll find the zipped up contents)
Drag drop these to ur desktop or anywhere u want them
NguyenHuu said:
I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?
Click to expand...
Click to collapse
push the file to sdcard of the device and using tar there after all it is also a linux system
diablo009 said:
Extract it to the file with no extension.
Open winrar.
Drag drop this file into that (u'll find the zipped up contents)
Drag drop these to ur desktop or anywhere u want them
Click to expand...
Click to collapse
great! thanks.
uskr said:
I recommend do this on a clear system, or that you do a factory reset once you reboot. The reason for that is that sometimes you get some data corruption during the force closes (corruption on the configuration files, not user data). But a factory reset fixes that.
Click to expand...
Click to collapse
Hi all,
I just did deodexed my atrix. Thanks much for the wonderful work~!!!
Mine has handful of apps installed prior to deodex. I was wondering what would be implication for not having clean system after deodex.
If you are looking for how to get back to stock Bell, go HERE.
Disclaimer: I have not tested this on anything but my phone. This is a development section of a hacking website. Make backups. Know what you are doing.
Credits:
Brut.all for apktool
edgan for 2nd-init
designgears for aroot inspiration.
xda for being a source of info.
Requirements:
Windows 7 or Ubuntu 10.10+ (10.10 and 11.04 tested)
Java installed. (For applymods, it uses apktool)
Running Phone, not in recovery mode, etc.
Tips:
Don't factory reset please if something goes wrong, it just erases your personal settings, it doesn't write to the system partition. It also deletes your data partition, making it harder to get back to stock.
Early usb mode, turn your phone on while holding down the lower volume button, when it says fastboot, release and press volume down repeatedly until it says early usb enumeration, then press up volume. It takes 30 seconds or so before adb is ready.
Version 9:
Download it here.
What's new:
Added support for 2nd-int (WIP, tested on stock Bell only)
shsu updated to allow a super user to become a super user, acts like sh in that case.
fixed linux install_recovery.sh and uninstall_recovery.sh scripts to use shsu instead of remaining using su. Ditto with ApplyMods.sh
Boot animation now smaller, using jpegs instead of png files, no difference in appearance.
Version 8:
Download it here.
What's new:
Added full phone backup and full restore phone options to the menu. It will download a backup if there is none found.
root script more universal, tries psneuter first, then gingerbreak.
Early usb recovery updated, now uses a tmpfs for system, also mounts /sdcard and /sdcard-ext.
Deodexed French 2.1.1 files incorporated.
Misc fixes
Version 7:
What's new:
New Menu script for windows and linux in the top folder, double click Menu and enter options.
ApplyMods and other scripts updated to use /data/local/tmp/system, this means I can update system.tar.gz and add folders to be copied into system.
Early USB enumeration recovery option. (experimental but useful as is)
Fixed bugs in windows scripts. Can't get user input from bat file while in a parenthesis block apparently.
Bloat backed up to sdcard now
root and unroot scripts updated with more prompts for rebooting phone.
Version 6:
What's new:
Support for Telstra 1.4.2.
ApplyMods can create signed update.zips now, Create_update.bat updated. both using basic ready made scripts in main bin folder instead of creating them on the fly, CR LF issues.
Updated root and unroot scripts, more fool proofing, has to be Bell stock firmware (psneuter doesn't work on telstra).
Includes basic boot animation, and mod for Bell apn on telstra firmware. (Have to reset to default under access point names in settings.)
transparent status bar, yellow tinted white for text color, matches front buttons somewhat.
Version 5.1:
Features:
Works under Linux and Windows 7
Includes root and no ads scripts
Patch system for applying modifications.
What's new:
New scripts for doing mods, fixes issues with patch 9 images.
Updated root and unroot scripts, more fool proofing.
New RestoreSystemPartition script
Custom apktool for more [hopefully] bug free installations.
How to use:
Extract archive, keeping folder structure intact.
run a command prompt/terminal (There is a link to one in the windows folder)
run root.bat or root.sh from the linux or windows folders, depending on which one you are using.
Turn the phone off after that is done and turn it back on again.
The rest of the scripts shouldn't be run with psneuter affecting the phone.
run ApplyMods.bat (.sh) [OPTIONAL] This applies webtop hack and translucent status bar, translucent notification drop down, etc. Select update system.tar.gz.
run install_bell_deodex.bat or .sh
System image of stock Bell.
Mirror of above
Cheers!
Very nice! Looks good!
Will try this when I get home
Sent from my Motorola Olympus
So what is the benefit of this? Will I be able to theme my device with some of the themes that are available? Or should I play it safe and wait for a bell. Sbf to leak before I try anything and brick my phone again lol thanks in advance
EDIT: i see that you have included soft_brick.bat is it the same as this one http://forum.xda-developers.com/showthread.php?t=982859 because that one did not work for me thanks again
Sent from my MB860 using XDA Premium App
cool, i'll try this tomorrow when i don't still have a ****load to do and only 5 hours to sleep
nice to see a Bell dev here!
Also I just wanted to say major props for the crazy awesome idea of doing over-the-air download and installation. Really smart and original.
Atrices, just so you know
NFHimself said:
Hi,
(What is the plural of Atrix?)
Click to expand...
Click to collapse
Can I run this on my mac? Sorry relatively new to adb
Sent from my Motorola Olympus
you could run it on a mac, just had to edit the script a bit.
Hi,
So what is the benefit of this? Will I be able to theme my device with some of the themes that are available? Or should I play it safe and wait for a bell. Sbf to leak before I try anything and brick my phone again lol thanks in advance
Click to expand...
Click to collapse
I wouldn't try theming with ATT files, I would take what was done to them and apply them myself to the deodexed files here. There may or may not be differences that are not obvious. I am never really sure if there is any benefit to this stuff, it's fun to do, about it.
EDIT: i see that you have included soft_brick.bat is it the same as this one http://forum.xda-developers.com/showthread.php?t=982859 because that one did not work for me thanks again
Click to expand...
Click to collapse
The soft_brick.bat script is specific to the folders I am using for transferring data to /system/app and /system/framework. It tries to get root via psneuter, mounts system read write, deletes dalvik-cache files, and tries to copy the files already on the phone to the right folders. It could be that just one file caused the phone to crash mid copy and copying it again will fix things. This avoids trying to do a usb data transfer of all the files which you don't have time to do otherwise. I was also thinking that install-recovery.sh would be a good place to do this, (and then clobber it later with the init.d hack) but I couldn't find setprop and I wasn't in need enough to select a file to use as a semaphore.
Can I run this on my mac? Sorry relatively new to adb
Click to expand...
Click to collapse
It would be easier to do it all from a sh script really, and that would likely be more compatible with a Mac.
Also I just wanted to say major props for the crazy awesome idea of doing over-the-air download and installation. Really smart and original.
Click to expand...
Click to collapse
Thanks!
Cheers!
maledyris said:
Atrices, just so you know
Click to expand...
Click to collapse
Thanks, a lot, really, 10 chars..
How do I recover from a softbrick from this? Thanks.
Before anything is done, all the files are extracted to /data/local/tmp/app and /data/local/tmp/framework. If you run into problems put the phone into fastboot/early usb enumeration mode (see here) and run soft_brick.bat (.sh for linux)
Quote:
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
This is the message I get when i run the batch file.
This is of course when invoking Early USB Enumeration.
Wait for the count down to finish ...
'TIMEOUT' is not recognized as an internal or external command,
operable program or batch file.
clearing Dalvik cache..
rm failed for /data/dalvik-cache/[email protected]*.dex, No such file or directory
rm failed for /data/dalvik-cache/[email protected]*.dex, No such file or director
y
rm failed for /data/dalvik-cache/[email protected]*.odex, No such file or directory
rm failed for /data/dalvik-cache/[email protected]*.odex, No such file or directo
ry
reinstalling apps
cp: cannot stat '/data/local/tmp/app/*': No such file or directory
reinstalling framework..
cp: cannot stat '/data/local/tmp/framework/*': No such file or directory
done.
The timeout message means you are running a version of windows without timeout, see adeo thread.
The lines for rm just mean there are no files to delete in the Dalvik-cache, which is normal, you should see that the second time around.
The cp lines are saying that there are no files in /data/local/tmp/app (/framework).
So, that's unusual, in order to get soft bricked using my script you would to have copied files from /data/local/tmp to /system, and if you are bricked would be unable to delete the files afterword.
sequence:
cd /system
cp /data/local/tmp/app/* app/
sync
reboot now
**brick**
So, how are the /data/local/tmp/app files being deleted?
No clue. I'm not sure what to do here? Is my phone permanently bricked? Any other way to recover from this? The one thing that could have gone wrong is I tried installing from my behind my works firewall. Maybe I could not download the proper files.
No, you are soft bricked, you only made a change (that I know of) in system files.
Were you rooted before you tried this?
If you copy the soft_brick.bat files and change the last line to be adb.exe shell ls -R /data/local/tmp, what do you get?
Basically, it sounds like to need to get the files copied over to data/local/tmp, how they are missing/inaccessible is odd. So, create a script to copy the files over bit by bit, might take a while but it should be able to be done.
EDIT:
Do this:
from command prompt:
adb.exe shell ./data/local/tmp/psneuter
wait a few seconds
type this:
adb shell ls -l -R /data/local/tmp
if psneuter fails, it isn't in /data/local/tmp, which is also odd.
I was rooted before this. So I should attempt all these commands while Early USB Enumeration right? That doesn't give me much time Lol.
OK, here's the output.
C:\bell_deodex>adb.exe shell ./data/local/tmp/psneuter
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
property service neutered.
killing adbd. (should restart in a second or two)
C:\bell_deodex>adb shell ls -l -R /data/local/tmp
/data/local/tmp:
-rwxr-xr-x root root 585731 2011-01-09 02:02 psneuter
-rw-r--r-- mot_tcmd mot_tcmd 4 2011-03-30 21:00 ap_tcmd.pid
C:\bell_deodex>^A
And sorry to be a pain. How would I create the script? What are the files that need to be copied? Are they included in your script?
↓ A new root method! ↓
There is now a new root method, that does not require downgrade!
http://forum.xda-developers.com/showthread.php?t=2180688
↑ Read this thread first! ↑
Prerequisites
A rooted LG O4X HD with a v10 firmware. (SuperSU preferred - personally tested)
Device adb drivers installed (so that a phone is detected as an ADB device when in B&R Recovery mode), adb itself is included in the archive
You need an installed Busybox! (/system/bin preferred, or need to edit bat file)
Warning: Do NOT do factory reset between step 1 and step 3! Otherwise /data/rootkit will be deleted, and you will have to start over.
Important note for linux users: bat files are for Windows. If you are using linux, i assume that it will be easy for you to open bat files and do commands by hand.
Step 0
Backup all your settings, and data from internal storage (!), cause factory reset (wipe) will be required.
You can try using LG's backup tool or Titanium Backup or anything else.
Also I'd strongly recommend removing SIM card and SD card from the phone.
Step 1
Make sure USB debugging is enabled (Settings -> Dev Options -> Debugging)
Connect your phone to your PC.
Execute file step0.bat and ensure that you grant su priv to ADB shell (2000).
Now execute file step1.bat - it:
- creates folder /data/rootkit
- copies busybox from /system/bin to /data/rootkit
- copies su from /system/xbin to /data/rootkit
- copies Superuser.apk from /system/app to /data/rootkit
- ensures owner and group of 0 for those files
- chmods files to required attributes (06755 for su, 0644 for apk, 0777 for busybox)
Result should be something like this: Note: In v2 i modified step1, so it tries to copy busybusybox from bin and xbin - one of them will fail, thats normal.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2
Upgrade your firmware to v20a. For example: http://forum.xda-developers.com/showthread.php?t=2069723
DO NOT DO FACTORY RESET! OR YOU WILL DELETE /data/rootkit FOLDER! DO STEP 3 FIRST!
Step 3
After successful upgrade shut down your phone.
Now, with USB connected (!!), hold volume up and power, and keep holding it at least until you hear windows "new device" sound.
You must see something like this:
Now execute file step3.bat - it:
- remounts system as writeable
- copies su to /system/xbin/
- copies superuser to /system/app/
- sets permissions on those files
Step 4
Now you can hold power button to reboot or just run step4.bat to reboot instantly.
Make sure that root is working, before doing factory reset!
Now you are STRONGLY recommended to do factory reset - or many things will mess up, such as lock screen settings or storage.
AGAIN warning, that factory reset WILL wipe internal storage, look at step 0
If you did all things correct, root will be kept (because it is on ro system partition now)
Step 5
Enjoy.
Note
If you are already at v20a and you want root, you can:
1) Wait for official release, with really unlocked BL - then it will be possible to install CWM -> get root
2) Wait until I make some interaction with B&R daemon in recovery
3) Wait for someone to find easier method
4) If you dont want to wait, you can go back to v10x (warning: all data will be wiped!), root phone, and do the procedure.
Any comments, notes, criticism or anything else very welcome!
Edit: In version 2 it tries to copy busybox from /system/bin and /system/xbin, thanks to AlderCass for pointing out
Nice work friend :good:
I don't have adb on my pc, is there a way to simply download the drivers? I ask because my current pc doesn't have the internet
Sent from my LG-P880 using Tapatalk 2
@non4 said:
I don't have adb on my pc, is there a way to simply download the drivers? I ask because my current pc doesn't have the internet
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
adb is included in the archive... i will see what i can do about drivers.
try to connect phone to your PC with debugging on and do "adb devices" from the folder with unpacked adb
if it sees your device - then good
@SkyDev
great findings, nice to see ideas expand to something useful.
did you also went all way and tried to install a changed/modified boot.img and add it to the LNX partition in /dev/block/mmcblk0p2 or /dev/block/platform/sdhci-tegra.3/by-name/LNX , it might just be our bootloader do work as unlocked and we can write unsigned boot / recovery img
edit;
i believe you can easily test it from recovery and su in here. even if you get security error on "boot", i think recovery can still be booted and you can recover the backup of the mmcblk0p2 partition (men always do backups)
Utterly fantastic work, and I'm sure this discovery will be the first huge step in truly unlocking this device. Congratulations!
Sent from my LG-P880 using xda app-developers app
skydev said:
adb is included in the archive... i will see what i can do about drivers.
try to connect phone to your PC with debugging on and do "adb devices" from the folder with unpacked adb
if it sees your device - then good
Click to expand...
Click to collapse
Isn't adb a pain to install? At least it was back in the day when I rooted my desire z with froyo thanks for the good work I will try get this to work on my own
Sent from my LG-P880 using Tapatalk 2
Dexter_nlb said:
@SkyDev
great findings, nice to see ideas expand to something useful.
did you also went all way and tried to install a changed/modified boot.img and add it to the LNX partition in /dev/block/mmcblk0p2 or /dev/block/platform/sdhci-tegra.3/by-name/LNX , it might just be our bootloader do work as unlocked and we can write unsigned boot / recovery img
edit;
i believe you can easily test it from recovery and su in here. even if you get security error on "boot", i think recovery can still be booted and you can recover the backup of the mmcblk0p2 partition (men always do backups)
Click to expand...
Click to collapse
Well, when now root is easily obtainable, you can do it
I think you are more experienced in all those things, i am low-levelly playing with phones only for 3-4 days so far.
I just dont want to trash stuff to the extent that reflash would be required.
Anyway i worked on the method almost 10 hours instead of sleeping at night, so now i think i going to go take some "Deep sleep" /10:46/
Anyway, i am noting again: if anyone also has disassembly skills, then you really should try to disassemble and analyze brd (backup and recovery daemon) - it runs at recovery with root rights, listens for commands on udp port, and probably can be used for "perfect root" (root without reflashing, and maybe even any LG device)
for people having issues using adb, you can download "terminal" from play , and do the same steps except do not start from a windows shell with adb
you just open the terminal.
secondly all files needed, should be tar'd instead, so the busbox more easily can unpack all files with proper rights instantly to the dest folder.
ie.
# cd /data ; tar xf /data/local/tmp/rootkit.tar
assuming rootkit folder is extracted and all files already was properly set with rights in linux when tar'ing the folder.
so conclusion
you do 3 steps to do this.
1. download rootkit.tar
2. open terminal on phone
3. cd to /data and extract(tar xf) rootkit.tar from where you put it when downloaded
this is all without adb used.
but you need adb in the end to run the bat file
Dexter_nlb said:
for people having issues using adb, you can download "terminal" from play , and do the same steps except do not start from a windows shell with adb
you just open the terminal.
secondly all files needed, should be tar'd instead, so the busbox more easily can unpack all files with proper rights instantly to the dest folder.
ie.
# cd /data ; tar xf /data/local/tmp/rootkit.tar
assuming rootkit folder is extracted and all files already was properly set with rights in linux when tar'ing the folder.
so conclusion
you do 3 steps to do this.
1. download rootkit.tar
2. open terminal on phone
3. cd to /data and extract(tar xf) rootkit.tar from where you put it when downloaded
this is all without adb used.
but you need adb in the end to run the bat file
Click to expand...
Click to collapse
Well, adb will be required anyway, and i want to keep freedom of choosing the su binary and Superuser.apk file.
The only requirement: su must grant root if called from recovery (when Superuser.apk is not accessible)
Also, why mess with terminal? You can easily misspell command, and they are long and important (because executed as root)
But idea with tar is good, maybe it will be required to do it this way, from B&R way.
I'm trying this method now and I noticed that a command in step1 fails on my system.
I changed:
adb shell su -c cp /system/bin/busybox /data/rootkit/
to
adb shell su -c cp /system/xbin/busybox /data/rootkit/
postacik said:
I'm trying this method now and I noticed that a command in step1 fails on my system.
I changed:
adb shell su -c cp /system/bin/busybox /data/rootkit/
to
adb shell su -c cp /system/xbin/busybox /data/rootkit/
Click to expand...
Click to collapse
Prerequisites
A rooted LG O4X HD with a v10 firmware. (SuperSU preferred - personally tested)
Device adb drivers installed (so that a phone is detected as an ADB device when in B&R Recovery mode), adb itself is included in the archive
You need an installed Busybox! (/system/bin preferred, or need to edit bat file)
Warning: Do NOT do factory reset between step 1 and step 3! Otherwise /data/rootkit will be deleted, and you will have to start over.
Important note for linux users: bat files are for Windows. If you are using linux, i assume that it will be easy for you to open bat files and do commands by hand.
Click to expand...
Click to collapse
Already mentioned in first post.
lukas77 said:
Already mentioned in first post.
Click to expand...
Click to collapse
I stated that I changed the line to work "on my system".
So everybody trying this will pay attention to that...
sry for this newbie ques,
but how to install adb drivers in our device..
jitesh22 said:
sry for this newbie ques,
but how to install adb drivers in our device..
Click to expand...
Click to collapse
There are many posts on these forums on how to do this - search for them, as this thread does not deal with that.
Everything works perfect, and now i have root on my JB .
Works like a charm! Thanks so much skydev! :laugh:
I upgraded to v20a with these instructions and now I have a rooted v20a.
Thank you very much skydev.
A picture for proof: http://g1303.hizliresim.com/17/7/ktz5m.png
I think we will be able to root when new versions arrive as long as we keep the /data/rootkit folder.
Edit: I upgraded to v20a with my LG PC Suite Version Hacker ( http://forum.xda-developers.com/showthread.php?t=2134192 ) and did no factory reset after the upgrade. Everything seems to work fine upto now.
quick and dirrrrrty
thats how i like it^^
well done
AW: [TUTORIAL] Keeping root after upgrade from v10x to v20x
Worked fine. There we're no problems. Did the kdz flashing via virtual machine with windows and the rooting part on mac os x since your scripts can be easily adapted. Also i dont have to care about adb or fastboot drivers.
Gesendet von meinem LG-P880 mit Tapatalk 2
First of all, many thanks for 4pda members.
It's time to post new thread for Lollipop.
This is for Kitkat me572c users.
(I can't make link so just copy the url)
● Lollipop firmware (UL-K007-WW-12.14.1.12) with root
Code:
mega.nz/#!LwJ3VBxK!4V4Ay-RzLS8x609zvyWL8IlcgI3xxfLcSqZ3gZkc52Q
● Install-Recovery.rar
Code:
mega.nz/#!C5ghzL6R!GR0WgLCumy6a429kB0ZjQOMxjPSylz07fVnHtKVm8ng
● ADB Driver
Code:
mega.nz/#!YAlxVbYS!7xfADRLuvcyO1GxRHtre3_e1TaVPmtIykqGbKCzUkkk
1) Can only be set on 4.4.2 (Kitkat). If you have already installed Lolipop, you must first revert to Kitkat. The computer should be installed ADB driver for the tablet and the tablet is turned on for the USB debugging. (no need to backup Internal memory. every data remain. but just in case, back up your data.)
2) Connect powered tablet to the computer. Download the firmware and rename it MOFD_SDUPDATE.zip, copy to the root of the memory card(MicroSd card) of the tablet. Download the archive Install-Recovery.rar and unpack it on your computer.
3) Run Install-Recovery.cmd, after the black command window turns up, volume buttons to select SD Download and power button for confirm. This will start the process of firmware.
Can anyone post instructions (in English hopefully because I'm lingual challenged) on how to revert back to KitKat if you've already upgraded to Lollipop? I didn't think that was possible...
Thanks so much!
I did a rough translation of the steps for downgrading in this thread. I haven't tried it myself, though, so I can't guarantee success.
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
does this work on ME176CX??
redhk886 said:
does this work on ME176CX??
Click to expand...
Click to collapse
I wouldn't try it. The process involves loading ROM images made specifically for the ME572C..
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
lexridge said:
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
gmaxjp said:
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
Click to expand...
Click to collapse
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
lexridge said:
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
Click to expand...
Click to collapse
Recovery is not CMW/TWRP, perhaps modified from stock.
Yep, What I did were execute series of command lines manually and crossing my fingers for several times
I'm expecting that will work in RPM based distros.
confirm, successful update using links/directions here.
kk stock rooted -> custom rooted 5.0 as above
yay!
significant speed increase in the ui animations, etc.
...google probably did a lot of support work for the moorefield
SacredMyths said:
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
Click to expand...
Click to collapse
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
gmaxjp said:
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
Click to expand...
Click to collapse
Good , no problem.
Now the only issue I'm having is a few emojis are black D:
where can i download the xposed apk for this model...
javcarbe said:
where can i download the xposed apk for this model...
Click to expand...
Click to collapse
Xposed Installer for Lollipop http://is.gd/jSVa1Q Use latest rev.
Since is a zip
How can I install a zip if I don't have a twrp recovery
---------- Post added at 06:17 PM ---------- Previous post was at 05:47 PM ----------
i unzip run the bat but doesnt work i need an instructions to do it manually
C:\Temp\XposedForZenFoneLollipop_20150607>InstallXposedFramework.bat
'
'
' Connecting ZenFone ..
'
'
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
'
'
' Pushing files ..
'
'
error: device not found
error: device not found
'
'
' Installing Xposed Framework,
' please GRANT permission for this script on your phone !
'
'
error: device not found
error: device not found
error: device not found
'
'
' Done, rebooting ..
'
'
error: device not found
Instructions fail with the recovery not being able to mount the SDCard for some reason.
But the zip sideloaded just fine.
Thanks.
Also, any idea what recovery is compatible?
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
javcarbe said:
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
Click to expand...
Click to collapse
I guess you just have to turn on usb debugging, connect your device to your pc and execute InstallXposedFramework.bat and InstallXposedInstaller.bat
I did and nothing
Like in description
Navibar 3 -5 -7 buttons mod - android 5.0
air3g, air 2
If you have my rom Lolipop ( mirek190 ) just plug USB and choose proper option.
On other rom make sure you have root and USB debugging on.
3 buttons navigation bar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5 buttons navigation bar
7 buttons navigation bar
air 3g
https://drive.google.com/open?id=0B8BF9-TGlz-FY2tWZUVZa05FU00
air 2
https://drive.google.com/open?id=0B8BF9-TGlz-FTEhvUTl2clE3Z3M
Ps - NOT RUN IT AS ADMINISTRATOR !
Hi mirek.
Can you add systemui.apk with a clock in its original position with 3 buttons?
Nope - center clock stays in the center like buttons
delete
Great job Mirek!
Hi, can you do this for the Air III? Do you need the stock SystemUI.apk?
EDIT:
I found this post www[dot]tsochen[dot]com/blog/post/15 and nearly the same intructions works for Air III M5C5. But the status_bar_*xml fix as not needed. This is the diff of navigation_bar.xml for 3 buttons
gist[dot]github[dot]com/kazuoteramoto/c0730bb27d0fb8dc6332
The system cannot find the path specified
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Wow, thanks, teramoto--this is fantastic! I just modded the SystemUI.apk on my device based on the tsochen link you provided, and your diff. I didn't want the screenshot and volume +/- buttons, but I did want to keep the menu button. So I just modded as indicated, and left the @id/menu entries untouched. The result is a nicely centered, four button variant.
EDIT: Somebody requested that I post my modded SystemUI.apk for a 4-button nav bar for the Air 3/III 32GB (M5C5). At the link below, I have done this, but also included 3- and 5-button versions, as well as the original 7-button SystemUI.apk version from the M5C5 v1.04 stock rom. The various SystemUI.apk files are obviously named by an explicit filename extension as you'll see when you download the archive. Also, let me reiterate--these are specifically for an Air 3/III 32GB (M5C5) tablet. Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing. Finally, and most importantly, note that credit for this goes to teramoto and the tsochen blog posting he pointed out above, which I just followed to do this, and also to mirek190 for starting this thread, and for helping out so many X98 Air users. Here's the link:
https://mega.nz/#!Hw0jRKBJ!0omuxVQXFHjzdbMV1bg6yvBhtMT570-gBhnkKxw2A4o
irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Facing the same problem...
irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Have you installed drivers ?
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
I did the same as you for whole day....thanks anyway.
irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
Thanks for a clue - 1st post updated .
verbage said:
Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing.
Click to expand...
Click to collapse
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
verbage said:
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
Click to expand...
Click to collapse
Hi. first let me thank you for your effort.
I tried your solution but I'm still without the buttons and notification bar.
Code:
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb shell
[email protected]_m5c5:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]_m5c5:/ # cd /system/priv-app/SystemUI
cd /system/priv-app/SystemUI
[email protected]_m5c5:/system/priv-app/SystemUI # ls
ls
SystemUI.apk
x86
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI # chown root.root SystemUI.apk && chmod 644 SystemUI.apk
chown root.root SystemUI.apk && chmod 644 SystemUI.apk
<
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI #
Am I doing something wrong? Any other idea? Or can I put the original file back?
Thanks for any help with this
EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
wepecko said:
I tried your solution but I'm still without the buttons and notification bar...Am I doing something wrong? Any other idea? Or can I put the original file back?...EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
Click to expand...
Click to collapse
Hmmm, from your ls -l command, it appears that the file ownership and permission were already set correctly, and so there was no need to give the chown/chmod commands again, but doing so didn't hurt, and only confirmed things.
My M5C5 is also on sikke1's rom--I started with mirek190's v6.1 slim version for the Air 2/II even though I have an Air 3/III, and it worked pretty good except for some hiccups. And so that is why I ended up on sikke1's debloated M5C5 rom, too.
Have you rebooted? You may be nervous to do so, understandably, but adb is enabled by default in the sikke1 rom so even if the graphical UI does not pop up, you can still do manual triage via adb.
---------- Post added at 07:19 PM ---------- Previous post was at 06:53 PM ----------
One thought for the future--if you are going to do this manually, you should stage it appropriately to hopefully avoid issues. For example, copy the original to a backup with the -p option to preserve file properties while still leaving the in-use original completely intact (i.e. "cp -p SystemUI.apk SystemUI.apk.ORIGINAL)". Then copy your modded apk file(s) into the same directory, and make sure file ownership/permissions are set as per above. Then do another cp -p to replace the in-use original with the modded apk.
Here's my listing for the directory to show you what I mean. I have the original apk plus the 3-, 4-, and 5-button modded apks all in the same directory with the correct ownership/permissions set. I can quickly change to any config, for example, the 3-button config, with a single cp -p command, i.e. "cp -p SystemUI.apk.MODDED-3-BUTTON SystemUI.apk". And there is no downtime/hiccup because one file is immediately replaced by the other, and the ownership/permissions are already correctly set.
Code:
[email protected]_m5c5:/system/priv-app/SystemUI # ls -la
ls -la
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-03 16:43 SystemUI.apk.MODDED-3-BUTTON
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk.MODDED-4-BUTTON
-rw-r--r-- root root 3572764 2016-01-03 16:43 SystemUI.apk.MODDED-5-BUTTON
-rw-r--r-- root root 3604448 2015-12-31 00:21 SystemUI.apk.ORIGINAL
drwxr-xr-x root root 2015-08-26 23:06 x86
[email protected]_m5c5:/system/priv-app/SystemUI #
Again, since you have confirmed everything, I would suggest rebooting if you have not done that. As I said, even if the graphical UI does not come up, you can still get into adb for repairs. At the very worst, you might have to reflash the rom.
I'm not sure why you have had hiccups, but these modded apks are directly from the stock SystemUI.apk of a v1.04 M5C5 rom. I have the modded navigation_bar.xml files, and I can send those or just diffs vs. the original so you can see the few lines that I changed. But you'll see they are just like described by teramoto and the tsochen blog he pointed out.
Thanks verbage. I understand your backup procedure and admit it was a mistake to rewrite the file directly.
However im still trying to find solution to this. I did restart ofcourse, several times, but it didnt help at all. It was late yesterday so i didn't have much time to try different scenarios. Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck.
One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?
Sent from my XT890 using Tapatalk
wepecko said:
Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck... One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
Hmmm, sorry to hear you are still having a problem. The 3-, 4-, and 5-button versions all work perfectly on my Air 3/III using sikke1's debloated M5C5 rom, and since you have the same device, any of the versions should also work for you.
Certainly, the 7-button stock original should work, too, and that is also included in the archive I posted.
Whether there may be a conflict with the xposed framework you have installed, I don't know as I do not have xposed installed on my Air 3/III.
Anyway, good luck with fix, and we'll wait to hear more.
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
wepecko said:
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
Click to expand...
Click to collapse
Great, glad to hear you have it working!