I'm running the latest Zero Hero rom and I managed to push a different resources once then I used my noob themere skills to give it the blur animations which failed and I had changed the build.prop with the maxisma 1 as it has native led support before pushing the resources.
So I reflashed and everything went back out of the boot loop that I had created with my botched framework-res editing but now I can't push anything becuz the phone keeps saying the file system is read only.
Any thoughts on how to fix my noob mistakes and actually get the blur animations to work without somehow making my file systems go haywire.
adb remount......
the bootloop could be caused by the incompatible build.prop file, your not just supposed to switch them between roms.....
B-man007 said:
adb remount......
the bootloop could be caused by the incompatible build.prop file, your not just supposed to switch them between roms.....
Click to expand...
Click to collapse
No actually it isnt its becuz my noob themer skills and me messing with the framework to get blur transitions the build.prop is running smoothly on this build and thx for the adb remount tip
Related
i flashed the zip via recovery and after i rebooted i had no service and the phone.apk wasnt working so i had to do a nanoid restore. Any ideas what i did wrong? im running DC 2.0.9.1 deodex rom
yep same thing happened to me,had to do a restore
Any ideas?
as far as i can tell it has nothing to do with with what you did, but rather it's a problem with signature matches, when Phone.apk is modified u have to resign it, and Android on startup seems to check the signatures and can tell they dont match what they should be and thus doesn't let the phone app load, which causes a lack of service... i'm still working on this but i dont know if there is a 'fix'... i'm hoping so. If you'd like to take a look at what i've done so far i have a thread in the main Q&A about custom phone apk on the hero....
i know this doesn't help a lot but i hope it clarifies some things
later today i'm going to try to resign every apk in my system folder... mainly just because i'm out of ideas, but hoping it works... who knows, hope i dont end up with a brick!
also it's important to make sure that if u don't go the update.zip route, when pushing any system app that you either do it from recovery or thru adb with the following commands
adb shell stop
adb push ????
adb shell start
after you issue the start command it may be a while but the phone kinda does a soft reset so ya anywho....
if im happy with my theme but i ONLY want the notification bar from another theme, is there a file that i can just take from the other theme & push to my phone to change it?
I don't think so. The notification bar is in the Framework-Res.APK? and if yo change that, you change the lock screen and a lot of other stuff soo yeah.
1-"adb pull /system/framework/framework-res.apk"
2-Copy the file you want from the "system\framework\framework-res.apk\res\drawable-mdpi\" folder from the ROM you desire into your pulled framework-res.apk in the same path as above "system\framework\framework-res.apk\res\drawable-mdpi\"
3-adb push "C,D,E:\(wherever it is)framework-res.apk /system/framework/"
just a heads up dont push framework you will get frosted boot loops.. flash the framework via update or mm
In my experience i've never had a bootloop from adb pushing the framework, and thats a lot of times!!
And i always push in recovery so the files are'nt being used.
icegad said:
just a heads up dont push framework you will get frosted boot loops.. flash the framework via update or mm
Click to expand...
Click to collapse
I've had this problem only on CM5. Not a big deal (I can just boot into recovery and use console to move them over), just an extra step.
This patch is to provide fully deodexed app and framework for users of the new 1.36.605.0 OTA (stock 2.1 Sense).
Nothing has been stripped out or changed, this is completely stock. To be clear, it is NOT a full ROM and will replace your /system/app and /system/framework folders completely. If you have added anything to these directories it will be removed.
As always, you should perform a nandroid backup before applying the patch.
http://www.multiupload.com/HAI18ED91X
<Insert usual disclaimer about not taking responsibility here>.
Worked fine for me. Initial boot took several minutes, so it appears your droid eye is frozen and it also got stuck at the HTC Incredible white screen for a few seconds longer too.
So far only problem The keyboard doesnt work. Get a FC on com.htc.android.htcime
Thanks for providing this.
Can't optipng keyboard folks...it will break it every time.
adrynalyne said:
Can't optipng keyboard folks...it will break it every time.
Click to expand...
Click to collapse
I ran HTC_IME.APK through xUltimate and deodexed it there and it works fine now.
I'll attach it here for everyone, seems to work just fine on my phone now.
just reboot into recovery. I suggest the free app on market called Quick Boot. It has option to boot right to recovery or bootloader.
Put HTC_IME.apk in your tools folder where ADB is located
adb shell
rm /system/app/HTC_IME.apk
exit
adb push HTC_IME.apk /system/app/
Deodexing is fine, the problem is when folks try to use optipng on it.
adrynalyne said:
Deodexing is fine, the problem is when folks try to use optipng on it.
Click to expand...
Click to collapse
Whats optipng?
It compresses the png images inside the apks. A lot of the deodex tools out there optimize (zipalign) and optipng as well.
This allows you to get the performance increase from zipalign, but lowers the size as well.
Zipalign actually increases the size of an apk.
this script is based on the work to Danesham90 and others see link
http://forum.xda-developers.com/showthread.php?t=598026
===============================================================================
Tested on the Samsung Vibrant, Script may need modification for other phones
===============================================================================
===============================================================================
Directions:
===============================================================================
the easy way:
1. turn on USB debugging
2. plug phone in to computer
3. run the script and follow the screen pormpts
the script will download everything needed to make a
signed deodexed clockwork flashable update.zip while also
adding root and the modified 3e recovery in the proccess.
===============================================================================
the hard way:
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
================================================== =============================
Code:
/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The **** You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://sam.zoy.org/wtfpl/COPYING for more details. */
UPDATED 02/03/2010
bug fix to signupdate.jar
clockwork script tweeks
UPDATED 02/02/2011
added upload to ROM to SDCard
added reboot recovery
added test sign all apk's in ROM - see README for details
added pull "/data/app/" and install "/data/app"
UPDATED 02/01/2011
added adb on by default toggle
added data wipe toggle
updated smali/baksmali to 1.2.6
UPDATED 01/31/2011
updated adb
fix similar filename deletion when using delete.txt
added barebones_delete.txt deletes everything that
does not cause phone to crash
UPDATED 01/29/2011
add "symlink dumpstate SYSTEM:bin/dumpmesg" to update-script.
add "symlink debuggerd SYSTEM:bin/csview" to update-script.
completed secondary method to make ROM from extracted Odin files.
see this post for instructions
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
UPDATED 01/28/2011
added auto delete apk's (bloat removal), edit bin/example_delete.txt and rename to delete.txt
added auto add apk's (pre-install or update apk's) add apk's to bin/apks directory
UPDATED 01/23/2011
fix path error when space in user name
UPDATED 01/22/2011
updated TempRoot.exe to not trigger anti-virus
updated Superuser.apk
This is fantastic! Thank you for always making things a little less troublesome.
Oooops, last minute change broke something, fixed and re-uploaded.
untermensch said:
Oooops, last minute change broke something, fixed and re-uploaded.
Click to expand...
Click to collapse
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Edit2: So it looked as though everything worked fine, but when I went to install it I got
E:Can't symlink /system/bin/cat
E:Failure at line15:
symlink toolbox SYSTEM:bin/cat
Installation aborted.
Whitehawkx said:
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Click to expand...
Click to collapse
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
untermensch said:
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
Click to expand...
Click to collapse
Yea I got the same thing as well. Thanks again, will give it another go.
Update: The process was more in-depth when deodexing. Signing went through np and when I flashed through clockwork it worked (goodbye splash screen!). There must be some issue with KA5 though. It got through to the Galaxy S screen and then started vibrating and then blackscreen. T_T
Thank god for this.. (Deodexer)
Thanks untermensch, your the best
Really really appreciate this. Thanks a bunch!
Most useful tool EVAR!
I T W O R K E D~!
My final attempt last night did not shoot out the "signed_ROM.zip" at the end. I ran it again this morning on KA5 and when it finished I had the signed_ROM.zip in the folder. Put that on my internal, flashed through clockwork and viola! Doedexed KA5 with root and modded 3e recovery. I can't thank you enough Untermensch for putting this together for everyone.
"Give a man fish feed him for a day. Provide him with tools to fish and feed him for a lifetime." (Yea I tweaked it but you get the idea!)
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Oh this is sick. i was looking for this all day the otherday when i was trying to deodex ka5! you rock and rule. i cant wait to explore the possiblities!
Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
can i use this to port a rom? forgive me if that is a noob question. just wanted to know if i had the right idea...
Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Whitehawkx said:
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
Click to expand...
Click to collapse
can you reproduce this error? I have seen it once but cant reproduce it
untermensch said:
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Click to expand...
Click to collapse
untermensch said:
can you reproduce this error? I have seen it once but cant reproduce it
Click to expand...
Click to collapse
Pretty sure the core.odex [null] error I got happened every time I ran the program. I ran it once after the 1:25am update and it happened. That is also the time it did not produce the signed_ROM.zip. I ran it again this morning after I saw the OP had been updated and it did produce the signed_ROM.zip but I still got the [null] error on core.odex. I'm going to Odin KA5 and do it again right now. I will let you know how it works out.
On a side note. I flashed the one I recieved this morning with everything being deodexed except the core.jar and it ran great until I deleted the odex file. Anywho, will test now. Also, not sure if this matters but I am running 32-bit Windows 7.
Update1: Initial news is good. Core.jar was deodexed properly with no errors. Will let you know how the entire process fairs once its completed.
Worked perfectly. I got no errors and everything deodexed properly. Flashed it on my phone and it's running just fine. You are awesome.
Thanks for retesting, glad it worked, there are thousands of files being generated
an lots of java processes being spawned so there are bound to be an occasional
error. I have added an automatic retry when there is an error to the next version
should be posted some time tomorrow.
I'm about 3/4 the way through testing this out - it seems to be working just fine with the exception that every command is appended with "ATTRIB" is not recognized as...
Hopefully it will work anyway.
One thing I noticed that might speed the script up in the beginning would be a root check, I have already rooted this rom but it still needed to run rageagainstthecage.
I've been looking for something like this forever now, thanks so much! Can't wait to play with it.
Sent from my SGH-T959 using Tapatalk
Hi, I want to ask some questions to you guys. Can somebody help me!
I have exposed in my Moto E4 Plus xt1770 Nicklaus. I trying to mod my battery icon, so I extract the framework.apk file in folder system, I changed the battery icon, and make new framework.apk (my mod), I replace and reboot. After boot I found nothing changed. I really confused from where the device get the default battery icon, because I had replaced that. But some is more interesting is, after that I can mount my data/system partition (I forget about data or system partition) in twrp, so I can't restore that with twrp. My device is work, but I can mount some partition in twrp so I think should be some trouble. Any way I have another case. I get flash my device. After that I rooting with magisk and install Xposed again, now I try changing boot animation. I replace the boot animation.zip in system/media and reboot. But I got the boot animation is not changed, from where the device got the default video, I had replaced . Any way I sure my procedure from all modding I do is right. So I start to thinking. I think Xposed can manipulate the system UI and framework,
so I wanna know are modding framework apk or systemui is have different way for device with Xposed n device without Xposed?
Sorry if my explanation is not clear, but can someone to help me for understanding what going on. Thanks:laugh:
I just flashing my phone, so I don't have XPosed in my phone. After rooting I tried replace bootanimation.zop in "dev/system/media", after reboot I found my boot animation still default. But deferent when XPosed installed in my phone, in case without XPosed, my phone doesn't have any issue like, Bluetooth share stopped, systemui stopped. I got my phone very normal after I'm using for couple hours.
So now I think I do wrong modding procedure,
*Are true if you want to change battery icon, you can do it with modding framework.apk (replace the default icon)?
*Are true you can change boot animation with replace boot animation.zip in "dev/system/media"?
I do that, but all still default. Huft...
I think, I don't wanna modding it any.
Actually I have made my own battery icon. I really want to use it. You know, I'm newbie. So it's so difficult n much time to made it .But now I give up, I got stuck.