Database Develop

Bootup Screen For Kyocera Zio M6000

First and foremost i want to thank esk02k and his friend for the images. All Credit goes to him for the images check out his post on xda called the thc weed leaf (i would post the link to his page but it wont let me says out side links are not allowed by new users but yet its an internal link). I didnt use all of them as there was only 37 images that i had to replace and i couldnt find the file that links to the boot up animation png files to add in the extra files so i used most of them and all i did was make it to the right size and converted them from jpg to png.
I am using the stock rom and my phone is rooted using universal androot version 1.6.2 beta5 (search for 1-click root for N1 to find this it will work on this phone) you have to install super user then you need root explorer found in the market. Now on to how to install this.
1) Install universal androot and the root explorer run universal androot to get your phone rooted you may chose soft root which only lets you temporary root till you reboot (dont worry it will not void your warrenty)
2) Download kyocera zio m6000.zip at the bottom of this post and extract it to a folder on your pc
3) Copy the folder to the root of your sd card
4) Open up root explorer and click on /data/FLEX/bootanimation
5) Copy Startup_Sound_M6000.ogg from the folder you copied to your sd card to the /data/FLEX/bootanimation folder overwriting the one in there
6) Next goto /data/FLEX/bootanimation/assets folder and copy all the png files from the folder you copied to your sd card to the assets folder over writing the ones in there
7) Exit out of root explorer and reboot your phone to see your new boot up screen and enjoy the first mod for this phone. (Note im not sure why the android screen dont show up no more when none of the files that was replaced was the android png files only the cricket png files are replaced)
Well there you have it the very first mod for this phone i hope you all like it as this is my first attempt at making a boot up screen animation im not sure how to make it animate more so please give constructive critisim do not bash it please and please tell esk02k thank you for all the hard work he did with the images all i made was the start up sound and resized the images and converted them to png to work on this phone so in all it only took me bout 7 hours his work was a ton harder and probably took him days maybe weeks. So major props to esk02k
**edit** Wow i started this by making the first mod for the phone and showed you all where to replace the stuff and got the ball rolling and not one thank you. Wow it shows me how much im appreiated here.

Everytime I try to copy the files, it says I do not have enough space. What do I need to get rid of?

muttd said:
Everytime I try to copy the files, it says I do not have enough space. What do I need to get rid of?
Click to expand...
Click to collapse
Remove some unwanted apps or apps that came on the stock rom that are worthless to you i removed the demo games that the company put on it and that gave me enough free space you need 6.50 mega bytes free to use this i made it as small as i could with out making it look like crap. you can remove some of the apps from /data/app i would recomend to back up the files before u delete them in case u have to put them back.

I have tried to copy the new pngs to the assets folder, but every time. I do, the original files replace the new ones. The closest I got was when I rebooted and I saw the first png of the original cricket boot animation, then it skipped all but the very last one of the new png I attempted to install.
Can anybody help me?
Sent from my Zio using XDA App

I am a new user of Kyocera Zio M6000. I also want to install the boot up screen for it. You describe the installation process clearly. Thank you for it.

SnakeFist said:
First and foremost i want to thank esk02k and his friend for the images. All Credit goes to him for the images check out his post on xda called the thc weed leaf (i would post the link to his page but it wont let me says out side links are not allowed by new users but yet its an internal link). I didnt use all of them as there was only 37 images that i had to replace and i couldnt find the file that links to the boot up animation png files to add in the extra files so i used most of them and all i did was make it to the right size and converted them from jpg to png.
I am using the stock rom and my phone is rooted using universal androot version 1.6.2 beta5 (search for 1-click root for N1 to find this it will work on this phone) you have to install super user then you need root explorer found in the market. Now on to how to install this.
1) Install universal androot and the root explorer run universal androot to get your phone rooted you may chose soft root which only lets you temporary root till you reboot (dont worry it will not void your warrenty)
2) Download kyocera zio m6000.zip at the bottom of this post and extract it to a folder on your pc
3) Copy the folder to the root of your sd card
4) Open up root explorer and click on /data/FLEX/bootanimation
5) Copy Startup_Sound_M6000.ogg from the folder you copied to your sd card to the /data/FLEX/bootanimation folder overwriting the one in there
6) Next goto /data/FLEX/bootanimation/assets folder and copy all the png files from the folder you copied to your sd card to the assets folder over writing the ones in there
7) Exit out of root explorer and reboot your phone to see your new boot up screen and enjoy the first mod for this phone. (Note im not sure why the android screen dont show up no more when none of the files that was replaced was the android png files only the cricket png files are replaced)
Well there you have it the very first mod for this phone i hope you all like it as this is my first attempt at making a boot up screen animation im not sure how to make it animate more so please give constructive critisim do not bash it please and please tell esk02k thank you for all the hard work he did with the images all i made was the start up sound and resized the images and converted them to png to work on this phone so in all it only took me bout 7 hours his work was a ton harder and probably took him days maybe weeks. So major props to esk02k
Click to expand...
Click to collapse
Apparently, the same number of images as the original must be used?
I tried one of my own, using boot screen found elsewhere on XDA that had more images. Didn't work.
Going to play around w/ the images today, reduce the count to the same as the original and see if that's indeed the case.
Or maybe it was the size of the images. I dunno yet.

Doesn't do a thing to my Cricket Zio.

hey i figure since your so gutsy can you get me a recovery rom my phone is crashed and cant find crap online

aago1254 said:
hey i figure since your so gutsy can you get me a recovery rom my phone is crashed and cant find crap online
Click to expand...
Click to collapse
We need a good solid backup rom, any post?

If your phone is a brick check the other zip threads for the update and you'll be on your way to a working phone
Sent from my from my rooted 2.2 no bloat Zio using XDA App

Zip threads?
Where can I find these zip threads?

ZIO threads. Like the 2.2 in the development section
Sent from my from my rooted 2.2 no bloat Zio using XDA App

Zip threads
Well, the 2.2 thread appears to refer to the windows downloader, with which I have two problems:
1) I don't run windows but linux, and
2) To do this, it appears I need to get into USB debug mode. I'm stuck in fastboot.
What I think I really need is the stock ROM from the Sanyo Zio. Does somebody here have this?

I can see if I can use adb to pull the 2.2 rom and if I have any luck I will let you know
Sent from my from my rooted 2.2 no bloat Zio using XDA App

Thanks
I'd really appreciate it.
You can email me too - justin at justinholmes.com

You may want to see if you can use a windows machine to update. I think you can do a virtualbox but I'm not 100%
Sent from my from my rooted 2.2 no bloat Zio using XDA App

I'm wondering if ReactOS is far enough along to run the updater. Will have to give it a try, liveCD.
No go. Booted the live CD, couldn't access any of the media devices to access the update tool.

Hmm
but listen, I can't get the phone into USB debug mode, so how can I run the updater? At the moment I'm stuck with fastboot. Normal boot is black screen, no response of any kind, no adb.

Turn the phone off, hold volume up down and power and your phone will bopt into modem download mode. Then update.
Sent from my from my rooted 2.2 no bloat Zio using XDA App

Umm wrong thread.
Try the android 2.2 thread. Lot's more helpful info there friend
jMyles said:
but listen, I can't get the phone into USB debug mode, so how can I run the updater? At the moment I'm stuck with fastboot. Normal boot is black screen, no response of any kind, no adb.
Click to expand...
Click to collapse
Sent from my Zio using XDA App

[TOOL] Auto-Deodexer/ROM builder 2.5.6.2 - UPDATED 02/04/2011

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

[MOD/HOW-TO] Remove hard key vibes via android.policy.jar

I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.

Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App

n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.

bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.

n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.

Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.

please delete

meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.

Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.

meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?

maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.

meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...

maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.

n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.

I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?

I have no problems with this mod. It works all fine.

Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you

It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..

I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..

lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App

[Q] Stop Auto VZW Auto Update

I found how for the X2 but the instructions dont work for the Revolution.
Anyone know the way to stop it?
Thanks

Using root explorer goto /system/lib/libdme_main and add .bak to the end of it. You will keep bluetooth and no more update. Make sure you do NOT mess with anything else!
Sent from my VS910 4G using xda premium

I deleted that file (adding.bak sounds much better) and it has gone away, just like mtmichaelson said.

Sweet thank. Ya on my droid 2 i stopped a bunch of stuff and just did the .bak so if i need it later i can just change it back.
Thanks

Just to double check, this works on revo phone.
When I acess file it has .so file type do I change .so to bak?

I just added .bak after the .so
Sent from my VS910 4G using XDA Premium App

Revolt - LTE
I'm not sure if this is related, but I noticed that after I flashed Revolt 1.3, I never see the "LTE" symbol in my notification bar. I'm in an LTE area, so I know it's available--does that mean my phone isn't running LTE anymore or is the symbol just not showing up on this ROM? I apologize in advance if this is a ridiculously misguided question--I'm new here and learning as I go.
By the way, mtmichaelson--I said this before and I'll say it again--awesome ROM! Thanks again for your hard work.

mtmichaelson said:
Using root explorer goto /system/lib/libdme_main and add .bak to the end of it. You will keep bluetooth and no more update. Make sure you do NOT mess with anything else!
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
will this also work for the updated Revolution (2.2.2)?
Thanks in advance

ally3447 said:
will this also work for the updated Revolution (2.2.2)?
Thanks in advance
Click to expand...
Click to collapse
Yes it does
Sent from my VS910 4G using xda premium

mtmichaelson said:
Yes it does
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
So, right now it is a .so file. Do I just add .bak to it, or change it from .so to .bak?
(Just want to be extra sure.)
Also,I would like to root my phone. I found a way that someone rooted theirs with their 2.2.2. Do you think I should root first, then change the file so it doesn't update? Or does it matter?
by the way, Here is the root I found(sorry it's a bit long):
"How to root your OTA Updated Revo:
This method requires you to downgrade your phone back to the V4 stock version. As of now, there seems to be no root process for the V6 update. This method has worked for me and I am also on a custom ROM that has been said to have some, if not most of the V6 updates included without the bloatware.
Step One:
- Be sure to get the following files:
---- LG VZW_United_WHQL_v1.2.0.exe
---- LGAndroidDriver_Ver_1.0_All.exe
---- LGNPST_Store_Lab-1.zip
---- VS910.dll (required to use LGNPST_Store_Lab-1.zip)
---- VS910ZV4_04.S4_04.P58008.R5.user.tot
---- RevoToolkit-1.0.apk (This is untested by me but supposed to provide an easier method to install CWM mod vs the ADB method)
---- SuperOneClickv2.1.1-ShortFuse (Includes the needed ADB program)
---- rageagainstthecage-arm5.bin (The exploit needed to root revo, not necessarily found with SuperOneCLick)
---- RevoltRom1.3.zip (This is optional, but recommended to speed up your revo and also to comply with the original topic of this thread. It 'seems' to stop the OTA from 'trying' the update since it includes updated features. NOTE that I said 'seems'... Other things I did may be the actual result I haven't seen the OTA try to install...
Ok, so to start, you will want to be sure that you have the drivers on your computer (I'm using windows 7 x64), so that is what this method has proven to work on by me.
Be sure to install:
- LG VZW_United_WHQL_v1.2.0.exe
- LGAndroidDriver_Ver_1.0_All.exe
Both may not be required, but I have both installed and things worked.
Then you will need to install:
- LGNPST_Store_Lab-1.zip
- VS910.dll (This is just copied into the folder LGNPST/Models. My install put the LGNPST program in C:\LG Electronics, not c:\Program Files (x68)... )
- You will run the LGNPST program, select the VS910.dll via Menu: File --> Select DLL.
- Then, in the bottom right of the LGNPST program, select BIN File (folder icon) to load the 'bin'.
--- This will require you to enter *.* in order to find the .tot file. Don't worry, this .tot file is what you need in the LGNPST Program.
- Once loaded and your phone is connected and recognized (Phone must be in 'Internet USB Mode'), hit the Start Button. This will begin the process of restoring your phone back to V4.
After that has completed, which takes a while, you will then need the SuperClick program to root.
- Copy, or verify, the rageagainstthecage-arm5.bin file is located in the Exploits folder where you extraced SuperOneClick.
- Run SuperOneClick, Select the exploit pull down (which defaults to 'auto') and select the rageagainstthecage option.
- Press the Root button and let it do its thing.
--- If it fails, this is what I had to do.. Reboot your phone. While it is rebooting, have the SuperOneClick program ready and waiting for you to hit Root again. As soon as the LG Logo becomes animated, hit Root and let it try again (While it is rebooting). This seemed to get the read/write options to work, where failed. This possibly is part of the update that is sticking around to stop you from rooting. So, try a few times. If/when succeeded, move on to the next steps if you wish to have some of the update 'fixes' without the update and a faster custom ROM...
To install a ROM, you need to have CWM installed.
Two methods to doing so seem to exist:
- The method I used was at this link: [RELEASE][6-14-2011] CWM Ported to the Revolution 4G! - xda-developers
Follow that and you should have a backup original image and the new image to get CWM to work to install custom ROMs
- The OTHER method, which is UNTESTED by me, is to use a simple tool called RevoToolKit, which is and APK file that runs directly on your phone. If it works, which others seem to say it does, this would be the most simple form of installing CWM to your phone. Be aware that this app is small, but uses a downloader to install CWM, so you want to make sure you have a good internet connection or data connection...
After that, you will want to follow the directions for CWM (ClockWorkMod) at this link:
- [Rom][8-17-11]Revolt Rom 1.3 - xda-developers
After all that, you should have a rooted Revo AFTER you managed to do the update.
I included links to some instructions in order to shorten up this post and not 'copy' someone else's methods and be sure that you can give the credit to them. The only credit I deserve for this is a complete step-by-step, in one place procedure to get you back or to root your Revo if you did the update.
In time, I am sure that there will be a simpler way to root the OTA Update, but until then, this is working for me and hope that this helps clear up some issues for others that find it tough to get back to root after the OTA Update."
It then has the file links, but I cannot post them since I am a newb.
Thanks again!

I don't see a way for you to change the file from .so to .so.bak without having root as far a rooting you only have to downgrade if your phone its v6 if out is running v4 all you need to do is root it
Sent from my VS910 4G using xda premium

Is there a way to do this without buying root explorer? I have bloat freezer so is there anything I can just freeze?
Thank You
*EDIT* just bought root explorer for $.99 through Amazon Appstore for those who still need it.

I'm on V4 and rooted back from V6 but it does not let me rename due to it being a read only file? sooo how do I add the bak? opened it with root explorer and it requested superuser privileges and I ok'ed it but when I go to /system/lib/libdme_main.so and try to rename it, it won't let me.

Sleepykat said:
I'm on V4 and rooted back from V6 but it does not let me rename due to it being a read only file? sooo how do I add the bak? opened it with root explorer and it requested superuser privileges and I ok'ed it but when I go to /system/lib/libdme_main.so and try to rename it, it won't let me.
Click to expand...
Click to collapse
On the top right of root explorer is a "Mount R/W" button. Click that and it should let you make changes to the system.
Hope it helps
"Home-Less and Iconic"

Thanks a bunch . That worked! I had pushed it at the system level. Didn't pay attention that I had to do it at the folder I'm in.

Sleepykat said:
Thanks a bunch . That worked! I had pushed it at the system level. Didn't pay attention that I had to do it at the folder I'm in.
Click to expand...
Click to collapse
Glad to help.
"Home-Less and Iconic"

[Q] how do you flash "framework-res.apk" without bricking the g1?

I was wondering how I could edit the framework-res.apk (it can be found in the /system/framework directory) file and not brick my phone, I've tried putting a modified version
in a signed zip file that was supposed to be for that very purpose, a stock update.zip for getting rc29 to 1.5(and yes, I did flash my phone back to rc29) and I recently tried to just take a file manager in root mode and copy-paste-overwrite, but I just soft-bricked my phone halfway into the process, probably because it was still mounted
P.S. I did mount the /system directory as rw
my phone:htc dream,no 2g-3g contract(wifi only),rooted (universal androot),stock 1.6 drc83(but I can get it to rc29,1.5 and crc43; at least I think thats the name of the second update),stock recovery,superuser elite+superuser- latest, su binary- latest, busybox- latest binary, and about 5000 scratches.
--edit-- can also get cyanogen recovery,and root through cm 4.1.99, and cm4.2.15.1.

So is your goal to root your g1? Have you followed any guides to root? Can you give just a bit more detail of end goal and a bit confused about what os you are currently running. Also its nice to get all info from bootloader screen
Sent from my HTC Vision using xda premium

reply
demkantor said:
So is your goal to root your g1? Have you followed any guides to root? Can you give just a bit more detail of end goal and a bit confused about what os you are currently running. Also its nice to get all info from bootloader screen
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I've actually already got cyanogenmod 4.2.15 on it so rooting isn't really an issue right now.
What I really want to do is theme my phone, because I really like the ICS buttons and black statusbar - but I want to wait until I'm more experienced
before I try to port cm7 to the g1 (as far as I know, cm7 is the first cyanogenmod to support themes).
P.S. since this is being sent from my g1 - I can't currently post my bootloader info; but I will as soon as I can.
Also. I want to know how I can sign the framework-res.apk after changing it to my satisfaction.

Sorry, reading my last post (although 2months old) I must have been trying to reply to someone else
You don't need to sign the framework-res
Just decompile with apktool, make changes, recompile (make sure to add the metainf and manifest from original back in) then you can create a flashable.zip to flash it and chmod, or add it to a ROM and sign the ROM or use adb when in recovery to push it and change permissions
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
Sorry, reading my last post (although 2months old) I must have been trying to reply to someone else
You don't need to sign the framework-res
Just decompile with apktool, make changes, recompile (make sure to add the metainf and manifest from original back in) then you can create a flashable.zip to flash it and chmod, or add it to a ROM and sign the ROM or use adb when in recovery to push it and change permissions
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
How would I sign the rom if I put it in one?
Apktool gives me errors when I try to recompile.
Ninjamorph from the market makes the changes, but they don't take hold.
P.S. perfect timing with the reply, as I posted my reply only about 45 min. ago!

If there are errors recompiling write those down and I'll take a look, as for as signing the ROM there are many ways, I use signapk for windows and one that amonra made for Linux, just Google search sign ROM android and you'll find many ways
Sent from my Nexus 4 using Tapatalk 2

Is there any posibility that I could just send you the rom I want to mod & a zipped folder containing a modified framework-res, and have you recompile/sign it? I just don't want to brick my phone. Thanks in advance!

If its a ROM for the g1 I already have it, how about just sending me your modded apk along with a link to the ROM and I'll make you a flashable.zip to install
And FYI, this isn't something that could brick your phone, recovery wouldn't be effected so worst scenario is you would end up in a bootloop
Sent from my Nexus 4 using Tapatalk 2

The rom is cyanogenmod 4.2.15.1 and I can't quite remember the link, but I'll post a zip with the frmwrk-rs and my email. Thanks in advance for the help!!

Here is a zip folder with the extracted/modified framework-res, if you don't have the rom I mentioned then ask for it in a comment.View attachment framework-res.zip

Sure, I'll take a look when I get home
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
Sure, I'll take a look when I get home
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Once you've signed/recompiled it, send the rom to me as a google drive/google docs file at [email protected] (or, if you know another better method, tell me) and I'll test it.

ok so finally got to a pc,
here you go
havent tested it at all, it recompiled but there was an issues with
framework-res\build\apk\res\drawable-land\Thumbs.db'
and
framework-res\build\apk\res\drawable\Thumbs.db
they were skipped but the rom should flash and whatever mods you made should be present other that this, dont have time to peek around and see what you did

demkantor said:
ok so finally got to a pc,
here you go
havent tested it at all, it recompiled but there was an issues with
framework-res\build\apk\res\drawable-land\Thumbs.db'
and
framework-res\build\apk\res\drawable\Thumbs.db
they were skipped but the rom should flash and whatever mods you made should be present other that this, dont have time to peek around and see what you did
Click to expand...
Click to collapse
Thank you so much for your time!
downloading......................
.......................complete!
flashing......

DREAMWAVE_devteam said:
Thank you so much for your time!
downloading......................
.......................complete!
flashing......
Click to expand...
Click to collapse
--edit-- (the best I can recall it saying)
finding update
opening update
verifying update
failed no verification (352 files)
update failed
installation aborted

Does the ROM flash for you with you current setup before the edited framework-res? What I mean, if you were to flash the update-cm4.... (Whatever the name) right now it flashes correct? With your current SPL, radio, and recovery. The only thing I did was recompile your framework-res, swap it with the one from the ROM you mentioned, rezipped and signed the ROM
I can't think of any edits you could have made to framework-res that wouldn't allow you to at least flash the ROM, may get stuck in a boot loop or never boot, but the ROM should flash
Sent from my Nexus 4 using Tapatalk 2

I looked inside the rom you sent me, and I didn't recognize any of it.
this is a link to the rom I got the framework-res from:
http://code.google.com/p/cyanogen-u...pdate-cm-4.2.15.1-signed.zip&can=1&q=4.2.15.1
from what I saw, the one you sent me looks more like a flash image than an update.zip,
if you look inside the one that I was talking about, it looks more like an ota, and I can flash it in cyanogen+jf 1.4 recovery which I got
from the flashrec app (not on google play anymore, from internet only).
I don't know if an unmodified version of the rom you sent me would flash, but the one you sent me seems to have problems in general.
No errors that would point specifically to the framework-res are appearing.
Here are the files that I modified: View attachment 2212696, decompile your own framework and paste/overwrite the contents over the contents of the res\drawable directory in the framework-res.apk.

I'm pretty sure that's the same ROM I installed you apk into, I'll be home shortly and take a look again, could have made a mistake
Sent from my Nexus 4 using Tapatalk 2

This rom that you gave me is about 10mb larger than the one I use, and takes 30 seconds to load in recovery and freezes everything momentarily.

@DREAMWAVE_devteam
yeah same rom, even checked SHA1 to make sure (with the ROM before i added your framework-res)
which is 1604kb compared with 5589kb of the original. so whatever was changed is what wont allow it to work
can you just quick go over how you decompiled and what changes you made, i know you linked something and ill look at it but i dont have a ton of time to dig right now so a brief overview would be nice