Related
Hi all,
I installed the SuperHero V3 Mas in my G2 (magic 32b) and it run so good and faster than all of others roms that I have tried. The problem that is the wifi cant turn on (it's normal this rom is made for G1).
Someone can help me to solve this problem and make this rom able to all G2 users.
The trick is to get and push the working wlan.ko (I think its in the sperhero 3 thread already) now why don't you tell me the trick you did to make this the fastest so I can try it
try pulling the wlan.ko file from a magic rom and pushing it through adb to /system/lib/modules, and im guessing its the fastest because he might have the magic that has the 288mb ram instead of 192, so virtually identical to the hero.
thank you for your response, I will try this right now
Thas is not work
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
I tried to change file access using chmod and I go this message:
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
please help
Ps: adbd is already running as root
co2gaz said:
Thas is not work
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
I tried to change file access using chmod and I go this message:
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
please help
Ps: adbd is already running as root
Click to expand...
Click to collapse
Try "adb remount" to mount /system as writeable.
Thank you for this information.
I tried it. the copy work OK, but the wifi problem steel here
I should have been more clear because pulling the file from any Rom isn't how you go about it. It has to match the kernel you are on and often even be further modified to the build. I think I heard either the wlan from superhero2 or the one from an earlier jachero worked. I just forget what one. Give me some time ill upload it. I had fixed and re-released this build.
Edit: Wlan.ko attatched. Belongs in system/lib/modiules
I thank you so math for your help,
I putted the file in my phone and i restart it, but wifi steel not work
Hi, I tried with JCAHero and it's same, very great rom, run so good on my magic G2, but the wifi not work
co2gaz said:
I thank you so math for your help,
I putted the file in my phone and i restart it, but wifi steel not work
Click to expand...
Click to collapse
Use the one I posted in this thread. I edited the post above ya. It should work then.
Thank you, I putted the new wlan.ko on my phone. now it seems better but it not work, now when I want to start wifi it show wifi is turning on during 4 or 5 sec, after that it show unable to start wifi.
if it was some link to explain how I can modify wlan.ko, maybe I can do some things (I'm java developer and I think it's native kernel file)
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
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.
Hi guys.
I know that the z4mod can successfully patch a Tab kernel, without any problems (I did it myself, flashed it, and ran it just fine for a few days).
But when I tried to run one of the zip files to switch the file system, everything went nuts and I had to reflash my Tab from scratch.
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
So if anyone around here knows anything about this sort of business, please take a look at it and let me/us all know, cuz it would be GREAT to get z4mod working on the Tab.
Here's the web site if anyone's interested;
http://www.sgscompilebox.dreamhosters.com/
Hi, did you tell ryanZA what results you got? I'm sure he'll be interested to help.
However, thank you for trying, I was about to do the same.
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
knightnz said:
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
Click to expand...
Click to collapse
RFS is Samsung's partition format (FAT + journal) that is supposed to be better for flash devices. Apparently it is not so good, and very laggy. Therefore people are switching partitions to ext2/3 or moving and linking stuff to SD card with ext2/3 or jffs2 partition.
jeebspawnshop said:
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
Click to expand...
Click to collapse
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Fyi: http://forum.xda-developers.com/showthread.php?p=9629477#post9629477
doloop said:
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Click to expand...
Click to collapse
It has been tested by many Galaxy S users. Go to their forum and you will know
evermick said:
It has been tested by many Galaxy S users. Go to their forum and you will know
Click to expand...
Click to collapse
I'm really newb on linux, but i've read a little since last post.
What if we:
1 - dump mount list from a working SGT (terminal or adb shell -> mount ?)
2 - apply Z4mod then SGT won't boot (i assume it creates /etc/.fstab)
3 - edit /etc/fstab to match the dump in step 1
But, how do we read/write /etc/fstab once the sgt is locked ? using some kind of update.zip, or is there some shell service we could connect to, even if some mounts aren't in the right place ?
Unfortunately, everything I could contribute to this idea was in my first post. I know absolutely nothing about Android development, sadly...
But after reading what Deodexed said about volumes not mounting properly during recovery (he's the guy trying to get CWM to work for our Tabs) it seems that maybe that's the reason that z4mod may not work... If the volumes aren't mounted correctly, it can't convert the filesystems.
Maybe what doloop said might work? I hope so. An SGT running on ext2 would rock the socks off anything else out there. God I want it
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