Database Develop

[HOW TO] Change ARC lockscreen to FULL - HERO ROM (update 10/06/2009)

tested on JACxHEROSki2.2 A.B.RMX & Drizzy's last HERO rom. Maxisma1.6.1
If your on HERO rom but hate the ARC lockscreen here's how to change it.
get the attached file, unzip *.apk and extract it to the root of your sdcard, then perfrom the following:
adb remount
adb shell rm /system/framework/com.htc.resources.apk
adb shell cp /sdcard/com.htc.resources.apk /system/framework/
adb shell reboot
or console
mount /system/
rm /system/framework/com.htc.resources.apk
cp /sdcard/com.htc.resources.apk /system/framework/
reboot
UPLOAD KEEPS TIMING OUT CHECK BACK LATER - IF ANYONE WOULD LIKE TO HOST THE FILE PLEASE LET ME KNOW...if you want the file please send me a PM

this should be the same for the hero build you are on, but since the last hero build i downloaded was new vision revision 2 for a friends phone, i don't have a more current hero. with that said
it was in data/app_s/HtcLockScreen.apk/res in that folder there are 4 drawables. each of them contains parts to it. i would imagine you could just drop that .apk into another hero rom, sign it, and flash it.
though i would definitely make a nandroid first

david1171 said:
this should be the same for the hero build you are on, but since the last hero build i downloaded was new vision revision 2 for a friends phone, i don't have a more current hero. with that said
it was in data/app_s/HtcLockScreen.apk/res in that folder there are 4 drawables. each of them contains parts to it. i would imagine you could just drop that .apk into another hero rom, sign it, and flash it.
though i would definitely make a nandroid first
Click to expand...
Click to collapse
thanks, what i actually ended up doing since both lockscreen.apk were the same i figured the "difference" i wanted laid somewhere else so through trial and error i figured it out.
it was the .com.htc.resources.apk from drizzy's rom that made the difference from an ARC lockscreen to a FULL lockcreen.
adb shell rm /system/framework/com.htc.resources.apk
adb shell cp /sdcard/com.htc.resources.apk /system/framework/
adb shell reboot
i should post a [how to] lol
UPDATED OP MADE MY FIRST HOW TO WOOT WOOT!!

wrong thread.

screenshots of this please?

johnnylicious said:
screenshots of this please?
Click to expand...
Click to collapse
a bit pointless to show screenshots of something that is not there. the lockscreen just shows the info that is normally on the arc, but no arc (the png files have been replaced with transparent versions)
Big thanks to the OP. I was doing this myself but didn't know enough adb to get my revised graphics back on to the phone.

Baldyman1966 said:
a bit pointless to show screenshots of something that is not there. the lockscreen just shows the info that is normally on the arc, but no arc (the png files have been replaced with transparent versions)
Big thanks to the OP. I was doing this myself but didn't know enough adb to get my revised graphics back on to the phone.
Click to expand...
Click to collapse
AGREED, this just removes the arc from your lockscreen and shows the complete image - leaving just date and time.
I'll post a screenshot later, I guess.

haha oooh i got cha i didnt undestand exactly what you changed or modifited to the lockscreen =D
i have the transparent lockscreen also on mine hero rom
thanks!

console commands
So i unziped it to my sd card, but I can't remember if i put it in the root of my sdcard or if its in /sdcard/downloads, but I don't know the console command to list the directories or files in that folder, i know on ADB/terminal emulator its 'ls'

NVM i figured it out, had to also type mount /sdcard because it kept saying no such file, but mount /sdcard did the trick

Has anyone got this to work on 1.7r2?

djunio said:
Has anyone got this to work on 1.7r2?
Click to expand...
Click to collapse
nope feel free to try it out.. just make a nandroid backup first using the recovery console if you have CM's new recovery image. if it doesnt work you can always just do a restore..
post back results

cest hero 2
My results on "cest hero 2" were well..take a look.

Kidd_Hanma said:
nope feel free to try it out.. just make a nandroid backup first using the recovery console if you have CM's new recovery image. if it doesnt work you can always just do a restore..
post back results
Click to expand...
Click to collapse
I did it seems like it worked but it gets stuck on the htc screen, I also tried to modify the file in 1.7r2 and that put me in a bootloop

does anyone know what hero built this resourse.apk is from?
im gonna test the resourse apk from drizzys elite and champion rom.
ill post back with results.

just tried it. none works. idk how to edit so im not gonna attempt to do it.

Follow up
djunio said:
I did it seems like it worked but it gets stuck on the htc screen, I also tried to modify the file in 1.7r2 and that put me in a bootloop
Click to expand...
Click to collapse
dont modify the file in the actual rom - you'll get stuck in a boot loop due to the rom needing to be resigned.
1.7 uses a new hero dump so it may not work.. My phone fell in Kool-Aid so im useless for the time being lol
johnowa636 said:
My results on "cest hero 2" were well..take a look.
Click to expand...
Click to collapse
looks okay but i notice the "AM" is off the actual time display
hiroots said:
does anyone know what hero built this resourse.apk is from?
im gonna test the resourse apk from drizzys elite and champion rom.
ill post back with results.
Click to expand...
Click to collapse
you may have done something wrong as this works with drizzys elite 100%

http://forum.xda-developers.com/showthread.php?t=538942&highlight=skinning+hero+app
Click to expand...
Click to collapse
can someone port the lockscreen from this thread to the new 2.8xxx builds???
the com.htc.resources.apk has some extra images added into this build which is causing the crash when u load in the old one

ok how do i reverse this i use twisteds hero i want the arc back

bigballa said:
can someone port the lockscreen from this thread to the new 2.8xxx builds???
the com.htc.resources.apk has some extra images added into this build which is causing the crash when u load in the old one
Click to expand...
Click to collapse
i have already done this - send me a pm and ill get you set up- im running it on jachero 1.8

Help to remove disastrous apk - please android Wizards

I REALLY need some assistance, think I screwed my phone, really want to avoid a hard wipe.
I installed Lockbot the other day, has some issues with dual lock layers (i.e. the lockbot app wasn't disabling my HTC lock so I had two unlocks.). emailed dev and he sent me a beta version to hopefully correct issue. I only received an apk file from him.
FYI I am on fresh 1.1, rooted.
I used the kitchen to puch this file: "LockBotPro_1.10.0_beta.apk" to /system/app.
The install went successfully, but later after a reboot I face a HUGE issue. The lockbot app is hanging upon reboot and will not unlock. At first I thought i would still be okay, I had ATK and Advanced Task manager both running at start up, so I can enter both of them through my notification drop down menu. I used both to kill the task-to no avail it is still locked. I tried to use advanced task manager to uninstall lockbot - to no avail, it cannot be removed.
Then I tried to pull back the file through kitchen, to no avail.
I don't know what to do. I cannot get my phone to unlock and i cannot pull the file off through adb or kitchen. DOES ANYONE HAVE ANY IDEA ON HOW TO FIX THIS??????

I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone

wtphoto said:
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
Click to expand...
Click to collapse
I have tried to pull the file in both adb and in kitchen. Would it have installed as something other than the name I pushed it under?

Even if the phone is hard locking (kind of rare of android. even in all the stupid f'd up things I've done I've only hard locked my phone to the point that I couldn't even get in to adb once or twice) then the file system is still completely accessible while it's booting up. You can use the "pull any file" from the kitchen and check off that you want it to delete it after it's done. Just get it all queued up in the kitchen and then power on your phone. Once it gets passed the HTC logo wait a few seconds and then run the pull file from the kitchen. Should work just fine for you.
The alternative (if you are comfortable with adb) would be to boot your phone in to recovery (can also be done through the kitchen, even when it's in the middle of booting) and then type the following from a command prompt:
adb shell mount /system
adb shell rm /system/app/your-application.apk
FYI for future reference you should push these types of applications to /data/app. Your hard locks could either be caused by the fact that the beta just broke things, or it could be that you have a copy of it in both /data/app and in /system/app.

the problem is that you dont want to just pull the file all that does is create a copy of the file where ever you pull it to you need to use the rm cmd to actually remove the file and have you tried to do this from the recovery menu before the phone boots? I mean I am by no means an expert but commonsence says that if you do it in the recovery menu that it would be gone when the phone actually boots and the problem would be gone.
edit: sweet im not a complete noob anymore I was right about removing from the recovery. flipz explained it better though.

thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!

TF1984 said:
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
Click to expand...
Click to collapse
I'll be here.

hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!

TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
You have a nandroid backup... don't you? Actually what you can try doing is flashing fresh right on top of itself. You won't lose any settings and it will overwrite everything in /system/app.

I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.

TF1984 said:
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
Click to expand...
Click to collapse
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).

Flipz I swear one day I am going to make a sizeable donation to you. If I can only find some extra money.
I think you have helped in every issue I have had after rooting, there haven't been many but you are always helpful when I run into trouble.

Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.

TF1984 said:
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
Click to expand...
Click to collapse
Might be worth it for you to try clearing your dalvik-cache to see if it fixes your FC's. If that doesn't work then my guess is you are using apps2sd and the symlink got broken somewhere along the way.
And no problem.

Yes I am using apps2sd. I tried the davlik clear cache in kitchen earlier today in attempt to fix the lockbot (I don't know, figured maybe it would work since i have no idea what that does to begin with).
Question, I did pull my sd card out earlier while the phone was off. Then booted and it only went into a boot loop, is that likely to have caused the FCs?
Does that mean that I cannot ever remove the sd card at all or will always cause this problem...cause that would friggin suck a big one!

flipzmode said:
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4942088&postcount=2 -- post #2 from the fresh rom thread from back in november.
The reason I don't like it is because it puts your phone at a huge risk of having problems once anything goes wrong. If you install a program that causes issues, a nandroid backup will not resolve the issue because the application is installed on your SD card not your phone. If your phone starts going crazy as reported here and here, then even just a restore possibly won't fix it. You might need to go as far as to wipe your SD card too. If you are lucky enough to have a restore fix your problems you will still need to reinstall every app, even if you didn't wipe your card. And on top of that when you try to reinstall any app it will think it's still installed, even though you restored your phone. But when you click "uninstall" it will just freeze half the time because there's nothing on the phone for it to actually install. I have also read many threads that say if you happen to boot the phone up without the SD card in then it will screw everything up.
Click to expand...
Click to collapse

yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?

TF1984 said:
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
Click to expand...
Click to collapse
Make sure you aren't forgetting the leading slash. /data/app not data/app. But no, nothing special. That should work. Although if using apps2sd you might want to push to /data/sd/app. It should work regardless because a2sd sets up a symlink but if your stuff is messed up then it might not be working right.

TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
Type this command in to mount:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
That will mount the /system volume and put it in read-write mode.
Once you are finished deleting the file, type:
umount /system
Then reboot the phone.
Edit: If you want to mount the /data volume, type: mount -o rw -t yaffs2 /dev/block/mtdblock5 /data

[Q] how do you install bootsound

Is it possible to get bootsounds working on my
Cm7 hero. I have tried a few zips I have found.
I get errors every time
Any help would be appreciated

Too busy to post it. It works. I have the files. Pm me and ill help later.

I would actually like to know how to do that as well.

OK here it is. I don't know if this works on sense, but it does work on AOSP based ROMs. Take the mp3 below and put it in /system/media, it's the THX movie bootup sound (I think). You can change it to whatever you want later. Take the sh file and put it on the root of your sd. Once both of those things are done, do this EXACTLY:
-open terminal emulator
-type "su" press enter
-type "cd /sdcard" press enter
-type "sh bootsnd.sh" press enter ONLY ONE TIME !!!
-type "reboot"
EDIT: no quotes obviously...
If you follow this, it will work. If you get smart and change it, or press enter twice where it says once, it will hose your /system. Oh, you should probably NANDROID FIRST.
Peace.
http://dl.dropbox.com/u/5669105/bootsnd.sh
http://db.tt/Jpn5NZ1 - thx sound

OMG! Yes! I love messing with terminal emulator. It makes me feel smarter than I actually am, lol. Thanks for the quick response.
Quick question - You said we should be able to change it afterwards so does that mean after we follow the steps you so graciously provided we should then be able to find an .mp3 somewhere in /system that can simply be replaced with another .mp3? for example maybe in /system/media/audio......?

You can use any mp3 you want.

il Duce said:
OK here it is. I don't know if this works on sense, but it does work on AOSP based ROMs. Take the mp3 below and put it in /system/media, it's the THX movie bootup sound (I think). You can change it to whatever you want later. Take the sh file and put it on the root of your sd. Once both of those things are done, do this EXACTLY:
-open terminal emulator
-type "su" press enter
-type "cd /sdcard" press enter
-type "sh bootsnd.sh" press enter ONLY ONE TIME !!!
-type "reboot"
EDIT: no quotes obviously...
If you follow this, it will work. If you get smart and change it, or press enter twice where it says once, it will hose your /system. Oh, you should probably NANDROID FIRST.
Peace.
http://dl.dropbox.com/u/5669105/bootsnd.sh
http://dl.dropbox.com/u/5669105/bootsnd.sh
Click to expand...
Click to collapse
I was gonna try this tonight, because I really want to grab the boot sound from the old Red Dawn Rom......but both of the dropbox links are the bootsnd.sh. If it's not to much trouble could you repost the THX mp3?

Thank you!

Oops. Fixed the mp3 link. I have the sense boot sound if you want. Not sure if it's the same as red dawn but let me know if you want that.

il Duce said:
Oops. Fixed the mp3 link. I have the sense boot sound if you want. Not sure if it's the same as red dawn but let me know if you want that.
Click to expand...
Click to collapse
Thanks for fixing that, and honestly with the 3D about to hit the shelves I'm downloading everything I can, before all these links start coming up 404...... So i'll take whatever's offered.

You know I think that link might be the sense 2.1 sound. I dont know where the thx one went. You could google sounds, change the name to android_audio.mp3 and your good.

il Duce said:
You know I think that link might be the sense 2.1 sound. I dont know where the thx one went. You could google sounds, change the name to android_audio.mp3 and your good.
Click to expand...
Click to collapse
Right you are, that was not the THX sound....Thanks for the guidance though, I now have it working. Off to try and make it work on my Nook. For anyone else trying to do this, the THX sound file you need is here........http://dl.dropbox.com/u/30200380/android_audio.mp3

hockeyfamily737 said:
Right you are, that was not the THX sound....Thanks for the guidance though, I now have it working. Off to try and make it work on my Nook. For anyone else trying to do this, the THX sound file you need is here........http://dl.dropbox.com/u/30200380/android_audio.mp3
Click to expand...
Click to collapse
Awesome, now just need a THX bootscreen

il Duce said:
OK here it is. I don't know if this works on sense, but it does work on AOSP based ROMs. Take the mp3 below and put it in /system/media, it's the THX movie bootup sound (I think). You can change it to whatever you want later. Take the sh file and put it on the root of your sd. Once both of those things are done, do this EXACTLY:
-open terminal emulator
-type "su" press enter
-type "cd /sdcard" press enter
-type "sh bootsnd.sh" press enter ONLY ONE TIME !!!
-type "reboot"
EDIT: no quotes obviously...
If you follow this, it will work. If you get smart and change it, or press enter twice where it says once, it will hose your /system. Oh, you should probably NANDROID FIRST.
Peace.
http://dl.dropbox.com/u/5669105/bootsnd.sh
http://db.tt/Jpn5NZ1 - thx sound
Click to expand...
Click to collapse
i followed these steps exactly and it worked perfectly scared the crap out of my wife with it she didnt know i added sound to the bootup she came running bringing it to me saying its making noises i think something is wrong.

question about changing the sound file does it matter the size or whether its an mp3 or a wma file. just overwrite the one i placed during setup? do i have to rerun the TE commands if i change the sound file? thanks for any answers to this
edit:crap shouldve just edidted my post above with this question sorry

Lol at your wife. You have to use mp3 only, memory size doesn't matter, but I think length does I think you want one that isn't too long, though I never tried a long one. < TWSS lmao. You dont need to redo the commands, unless you flash a new rom. Then you have to redo the whole thing.
sent from a series of tubes.

spleef said:
question about changing the sound file does it matter the size or whether its an mp3 or a wma file. just overwrite the one i placed during setup? do i have to rerun the TE commands if i change the sound file? thanks for any answers to this
edit:crap shouldve just edidted my post above with this question sorry
Click to expand...
Click to collapse
Any mp3 file will work as long as its renamed to android_audio.mp3 and placed in /system/media. I recommended an mp3 file no longer than 20-30 seconds at the most. I'm not sure if wma files will work as that's a windows file.
You do not need to run the commands in TE again unless you nandroid back or possibly wipe everything.
Note: This is just from my own personal experience. I'm not a developer or anything and I take no responsiblilty if you screw up your phone. I hope this helps and don't forget to nandroid first
EDIT: lol sorry Duce, you posted sometime in the middle of me typing on my phone
Sent from my pimped out HERO200 using XDA App

kewl going to play around with it thanks a bunch for the speedy responses
Sent from my HERO200 using XDA App

spleef said:
i followed these steps exactly and it worked perfectly scared the crap out of my wife with it she didnt know i added sound to the bootup she came running bringing it to me saying its making noises i think something is wrong.
Click to expand...
Click to collapse
Thats hilarious! I love it

Incase you get a permission denied error, just do chmod -x bootsnd.sh

[Q] how to enable init.d support

I'm using the the stock 2.3.4 from Spice website and this is by far the best considering wifi important.
My question is, can we enable init.d support or we need a special kernel for that?
I tried a tut. from zeppelin but failed miserably...
Any idea guys???

whyzee,
I followed this http://forum.xda-developers.com/showthread.php?t=1017291 and was able to use init.d without any issues.

cowsgo said:
whyzee,
I followed this http://forum.xda-developers.com/showthread.php?t=1017291 and was able to use init.d without any issues.
Click to expand...
Click to collapse
Thanks for the link but that was the one I tried without success .... Should try again when I have some real time...

whyzee
did you get an error when you ran the script? If you didn't then get root explorer from the market and see if you have the folder. It should be in the \system\etc folder. When I ran it I had no issues and followed the instructions that were on the page. Dumb question, did you reboot your phone once you ran this? If you got a error then you could try pm Zep and see if he has ideas that might help.

cowsgo said:
whyzee
did you get an error when you ran the script? If you didn't then get root explorer from the market and see if you have the folder. It should be in the \system\etc folder. When I ran it I had no issues and followed the instructions that were on the page. Dumb question, did you reboot your phone once you ran this? If you got a error then you could try pm Zep and see if he has ideas that might help.
Click to expand...
Click to collapse
The script you are executing is not meant for our device. Its trying to mount system partition as mtd type, while we need emmc partition type. Also, our device does not have moto-boot-mode file which this script is trying to replace.
So my suggestions are :
If you are using MIUI or CM, then they already support init.d scripts. (I guess)
Or
If you are using stock or andro - id then just copy following code in post boot.sh (something like that) found in /system/etc/, at the end of file.
Code:
for BOOT in "/system/etc/init.d/"*; do
.$BOOT
done
P.S. Note that you have enabled executable permission for all of your scripts placed in /system/etc/init.d
Sent from my CSL-MI410 using XDA App

Thanks for the replies guys, I've jumped to MIUI 1.10 now and as Napstar said it natively supports init.t...

whyzee said:
Thanks for the replies guys, I've jumped to MIUI 1.10 now and as Napstar said it natively supports init.t...
Click to expand...
Click to collapse
hi
correct me if im wrong. To my knowledge u need init.d to use apps2sd so u can put ur apps on ur SD and now since our phone has around 1GB phone storage which i feel is more than enough to install all the apps u need I dont see a reason why we need the init.d

haree said:
hi
correct me if im wrong. To my knowledge u need init.d to use apps2sd so u can put ur apps on ur SD and now since our phone has around 1GB phone storage which i feel is more than enough to install all the apps u need I dont see a reason why we need the init.d
Click to expand...
Click to collapse
init.d is a folder on /system/etc folder which runs whatever scripts you put in it during boot.....

[TOOL] The O2x Nullifier 2.2 - Single & Dual Passes!!! P990

Hello my fellow Android crack flashers! So Volk and I have wrote(him) and tested(me) his g2x nullifier for our phones. Well it works flawlessly! Which his thread is here. So with our learning adventures he has helped me port it to the O2x. So here is the run down. This was originally created as the g2xscrubber was insufficient enough for our flashberry addiction, and on top of that if wouldn't wipe our /cache either.
So the domino effect has begun. This is a simple script that will wipe your internal partitions cleaner then a whistle and get it dam near like new status, perfectly ready for a ROM. Like as if you just purchased it and didnt have any data on it nor a ROM and needed to be flashed. And yes it came all tricked out like that with CWM and all.. haha
So here it is...
The O2x Nullifier
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does something. It also formats the partitions afterward, including /cache too! Enjoy!
Some brief need to knows:
1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it. I've ran this Nullifier like 20 times in the last two days of first testing and on average its about 1204 seconds or about 19.8 minutes, on average. The Single pass zip is only half of the time of course. Or you can just watch the progress bar. After 20 times of nullifing and log pulling in 2 days, im pretty dang sure the bar is accurate. So enjoy!
2. ONCE THE NULLIFICATION PROCESS HAS BEEN COMPLETED DO NOT, I REPEAT, DO NOT TURN OFF OR LET YOUR PHONE DIE BEFORE FLASHING A ROM OR RESTORING... or you will brick your phone.
3. I will provide help, support, etc. for this, but as always flash at your own risk and I am not responsible if you turn your phone into your next non-aerodynamic frisby.
Enjoy!
Also I have now decided to copy the log to sdcard at completion (thanks to DARKSIDE for the idea). But from now on the log created in /tmp while in cwm is now copied to sdcard as O2x-Nullified-recovery.log. So it will still be deleted from RAM but never lost any more!!!!! muhahahahahahah... love it!
Thanks go to Волк aka Volk for letting me test and learn from his G2x Nullifier script. And also to owain94 for helping me make sure that this thing will run ok on the O2x, since I dont actually have the O2x..

Also if is doesn't work, please we need logs. You need to use a file explorer or put the external sdcard into your pc and grab and upload or pm me the log from your sdcard the file will be named 'O2x-Nullified-recovery.log'
mini change log:
1.2 -> fixed sleep command, 1.2
1.3 -> updated binary script and added /cache info per vadonka's advice
1.3.1 -> Bad zip... reupped
1.3.2 -> zipped with 7zip should work now.. dumb winzip... reupped
skipped to 1.5 -> updated script and binary. Also removed /cache format command; instead do a manual wipe for now
skipped to 2.0 -> updated script and binary again. Manual format still.
2.1 -> No more manual /cache wipe and working progress bar!
2.2 -> Single/Dual pass zip options. Thanks to Volk for error check and darkside for log creation idea. Added support for su660

nice work mate!

Ok so i'm hijacking this post to use while i'm at work (with crappy lowest bid PC) and using this FOR MY TEST UPLOADS ONLY. THIS WILL CONSIST OF G2X TESTS GETTING READY FOR THE O2X... DO NOT DOWNLOAD ANY ATTACHMENT ON THIS POST OR ATTEMPT TO FLASH IT BECAUSE IT WONT WORK FOR YOU UNLESS YOU HAVE A G2X!

Thanks a lot mate

da-pharoah said:
This was originally created as the g2xscrubber was not sufficent enough for our flashberry addiction.
Click to expand...
Click to collapse
Remember to read first, if your question hasn't already been asked or answered, ask and maybe you'll get it posted in the Q&A post.
Pharoh, what did you fix I see nothing wrong.
>.>

carburano said:
Thanks a lot mate
Click to expand...
Click to collapse
No worries
Волк said:
Remember to read first, if your question hasn't already been asked or answered, ask and maybe you'll get it posted in the Q&A post.
Pharoh, what did you fix I see nothing wrong.
>.>.
Click to expand...
Click to collapse
lol nice catch.. was in a hurry to leave from work. Fixed now.

Hi friend...
just tried but it's not working... E: Can't Open /sdcard/O2x Nullifier beta 1.zip (bad) Installation Aborted...

Interesting, there will be a log in cache/Recovery can you send it to one of us and we can have a look. It may have not been zipped correctly. Or heck, I'll dl it right quick and have a look.
Ah, it's not signed. One sec.
new link.
http://db.tt/YeuzWktM

Error status 6...
Did you made the updater script in Linux, mac or windows?
If Mac or windows what text editor did you use?
Did you ever edited the updater script if yes what text editor did you use?
Sent from my LG-P990 using xda premium

owain94 said:
Error status 6...
Did you made the updater script in Linux, mac or windows?
If Mac or windows what text editor did you use?
Did you ever edited the updater script if yes what text editor did you use?
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
used win7 and notepad++
error with op link or updated link by Волк?
carburano said:
Hi friend...
just tried but it's not working... E: Can't Open /sdcard/O2x Nullifier beta 1.zip (bad) Installation Aborted...
Click to expand...
Click to collapse
Волк said:
Interesting, there will be a log in cache/Recovery can you send it to one of us and we can have a look. It may have not been zipped correctly. Or heck, I'll dl it right quick and have a look.
Ah, it's not signed. One sec.
new link.
http://db.tt/YeuzWktM
Click to expand...
Click to collapse
OP updated thanks again Волк!

Why not just use the nvflash based v10b flashing released by Paul on modaco. I use that when I really want to clean everything up. Since it is V10b, easy to install CWM recovery using psneuter (thought it is not required) and can be done with a simple dd command directly.

hackworks said:
Why not just use the nvflash based v10b flashing released by Paul on modaco. I use that when I really want to clean everything up. Since it is V10b, easy to install CWM recovery using psneuter (thought it is not required) and can be done with a simple dd command directly.
Click to expand...
Click to collapse
Well really thats kind of a longer process.. thats a rom, this is just a tool to wipe clean your internal storage. Basically take it back to like new status, but still having full root ability. CWM will flash the rom of your choice after your done with the nullification process and manual /cache wipe. This will not take you back to a predetermined state (in terms of a rom), it will leave your phone a nice paper weight however until you decide to flash a rom.

nice work!
i have a little advice for you. use this method for the cache wipe and no need to manual wipe cache anymore
unmount("/cache");
run_program("/sbin/mke2fs", "/dev/block/mmcblk0p2");
run_program("/sbin/tune2fs", "-O", "extents,uninit_bg,dir_index,has_journal", "/dev/block/mmcblk0p2");
run_program("/sbin/e2fsck", "-fy", "/dev/block/mmcblk0p2");
run_program("/sbin/tune2fs", "-o", "journal_data_writeback", "/dev/block/mmcblk0p2");
run_program("/sbin/e2fsck", "-fy", "/dev/block/mmcblk0p2");
this create an ext4 partition, if you want ext3 just skip the first tune2fs row, and use the -j option in the mke2fs.
mke2fs recreate a new empty partition no need to fill with zeroes before, so the nullifying parts is unneded, just use the mke2fs. its enough, except if you want to wipe the data for reason.

I still receiving get the error message:
E: Can't Open /sdcard/O2x_Nullifier_1.2.zip (bad) Installation Aborted (Status 6)
Click to expand...
Click to collapse
What I'm doing wrong?

ev!denz said:
I still receiving get the error message:
What I'm doing wrong?
Click to expand...
Click to collapse
its because the update-binary is a bit old
use a newer update binary.

vadonka said:
its because the update-binary is a bit old
use a newer update binary.
Click to expand...
Click to collapse
How can I use a newer one?

Darn it! Ok im on my way to work.. I'll see if I can get around the limitations there an update for y'all...
Sent from my LG-P999 using xda premium

ev!denz said:
How can I use a newer one?
Click to expand...
Click to collapse
just replace the update-binary file in the META-INF\com\google\android\ directory
pull it from the cm7 kang for example.

vadonka said:
just replace the update-binary file in the META-INF\com\google\android\ directory
pull it from the cm7 kang for example.
Click to expand...
Click to collapse
OP updated