Has a ROM been made for the device yet?
As soon as one is made I will be one happy user as this tab has soooo much potential to be great
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Yeah i know i need one now lol
bkundert21 said:
Yeah i know i need one now lol
Click to expand...
Click to collapse
Why? What would you like a replacement firmware to do? Remove bloat? Do that with titanium backup (or anything else that can 'freeze' pre-installed crud.) Change the launcher? You can already do that (but it seems most of the replacement launchers are designed more for phones.)
What do you want different that you can't already change?
garyd9 said:
Why? What would you like a replacement firmware to do? Remove bloat? Do that with titanium backup (or anything else that can 'freeze' pre-installed crud.) Change the launcher? You can already do that (but it seems most of the replacement launchers are designed more for phones.)
What do you want different that you can't already change?
Click to expand...
Click to collapse
I gotta say I agree with Gary. Now that we have root and CWM (thanks to Gary) there's not much more I feel compelled to change I can already with root. Perhaps a custom kernel we can OC but this danged this flies now. Perhaps someone can come up with something that'll amaze us all (and that would be very cool!) and I'll be all over it. Right now with ICS looming it might be a better allocation of dev resources to just lay back and wait/see what that brings?
Now custom themes.....THAT would right now peek my interest. Learned a few things from hatman41 on the TF. This might be an excuse to dig back in.
Just an opinion.
skeeterpro said:
I gotta say I agree with Gary. Now that we have root and CWM (thanks to Gary) there's not much more I feel compelled to change I can already with root. Perhaps a custom kernel we can OC but this danged this flies now. Perhaps someone can come up with something that'll amaze us all (and that would be very cool!) and I'll be all over it. Right now with ICS looming it might be a better allocation of dev resources to just lay back and wait/see what that brings?
Now custom themes.....THAT would right now peek my interest. Learned a few things from hatman41 on the TF. This might be an excuse to dig back in.
Just an opinion.
Click to expand...
Click to collapse
I'd like to see a r/w external sd card. Having it be read-only is forcing me to change my process of working. But I do agree with the others, with root and cwm the tab is very very good.
otamctech said:
I'd like to see a r/w external sd card. Having it be read-only is forcing me to change my process of working. But I do agree with the others, with root and cwm the tab is very very good.
Click to expand...
Click to collapse
Really? I can change r/o to r/w and back again with Root Explorer in extStorages
skeeterpro said:
Really? I can change r/o to r/w and back again with Root Explorer in extStorages
Click to expand...
Click to collapse
yes i can do that also, but even when it is in r/w, i cant say, save an excel file to the card using quickoffice or any other app for that matter. It will only let me save to the built in storage
otamctech said:
yes i can do that also, but even when it is in r/w, i cant say, save an excel file to the card using quickoffice or any other app for that matter. It will only let me save to the built in storage
Click to expand...
Click to collapse
Interesting. I was just able to copy/paste from root to a folder on the exStorages and copy a file from the internal to the exStorages (an apk and an ePub)
Just re-read your post. From an app to exStorages. Hmmm...will try that.
Don't have quickoffice but polaris has very few options. Almost too few.
otamctech said:
I'd like to see a r/w external sd card.
Click to expand...
Click to collapse
I'd like to see that as well, but it'd probably be a kernel change, not what people here call a ROM change. Let's see, here's how it's currently mounted:
Code:
/dev/block/vold/179:17 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
It's already mounted as read-write. The thing that's preventing normal user write access is the uid/gid combo with the fmask/dmask (not sure why samsung didn't just use a umask instead of both of the other masks.) Essentially, what that is doing is say that all the files and directories (including the root of the mount) are readable by anyone, but only writable to the "system" user, or a user in the "media_rw" group. I'm going to take a wild guess that the "camera" application, the "my files" application, and other samsung apps are in that "media_rw" group. (not sure how to check that...)
Interesting... I'm trying to remount it manually (mount -o remount,...) and while it's not giving any error, it's not working either.
I'm not sure how these "vold" mounts work, what options are valid for them, etc. It's an interesting issue, though...
All I want is a deodexed rom. Might have to break out android for dummies and learn how to.
Once we get that then let the theming begin.
Sent from my Insanity powered SGS2
Not to difficult i may give it a try soon.
deodex'ing honeycomb stuff isn't as easy as gingerbread and prior...
garyd9 said:
deodex'ing honeycomb stuff isn't as easy as gingerbread and prior...
Click to expand...
Click to collapse
I know, thats why I havent learned it yet lol.
However I am slowly figuring out theming while the rom is odexed. Got a few things going now
This device is powerful and awesome. Id love to be able to change themes and icons. The bloat ware doesn't get into the way and slow performance down. This devise will do me good for about 1 year to 1 1/2 years than ill upgrade to a new more powerful device.
this may help..
http://forum.xda-developers.com/showthread.php?t=1373131
I will likely wait for a clockwork recovery to start ripping stuff apart.
this is my first sammy product, wife has a cappy that I flash. nota huge fan of touchwiz but its easy on the eyes compared to my past 2 devices, dell streak 7 & 5.
Moving this to a proper forum.
chrisrotolo said:
I will likely wait for a clockwork recovery to start ripping stuff apart.
Click to expand...
Click to collapse
Which model do you have? GT-P6210 (wifi only), GT-P6200 (international 3G) or SGH-T869 (USA/TMobile 3G)?
There's no CWMR for the p6200 (yet), but I've already done them for the other two.
P6200 3G from malaysia. no rush, patiently waiting. Im more than willing to help with any info needed. Thank so much.
chrisrotolo said:
P6200 3G from malaysia. no rush, patiently waiting. Im more than willing to help with any info needed. Thank so much.
Click to expand...
Click to collapse
Are you fluent with a shell prompt? If so, in order to attempt a CWM recovery (based on what I've already done for the p6210 and t869), please run the following two commands as root via adb shell... (and copy the resulting information)
mount
cat /proc/partitions
.. that will give me a hint as to which partition is probably your recovery partition. Send me that info IN A PM. I'll respond via PM with some more commands (based on the info you send me, I'll need you to dump a partition or two and get the images to me.)
Once I have the proper information and images, I can PROBABLY make a successful CWM recovery image (but please understand that I'll have to recompile a kernel BLIND with no possible way to test myself.)
Take care
Gary
---------- Post added at 11:43 PM ---------- Previous post was at 11:40 PM ----------
I should also mention that I'm going to be VERY busy over the next 3 days, so even if I get the images and all works okay, the earliest I'd be able to have a recovery would be Thursday or so.
Related
I just saw this!
http://twitter.com/unrevoked
They're currently working on one that will write to /system.
Stay tuned!
Thanks guys! Awesome work!
VoXHTC said:
I just saw this!
http://twitter.com/unrevoked
I downloaded an .apk file and I'm staring at it now..
Click to expand...
Click to collapse
I'm not very happy with installing and running things on my phone without knowing quite what they do. you go first
Yeah, report back if it breaks anything. I wanna root mine and this way seems easy.
LOL no way.. u 1st.
It worked, but unfortunately it has to be applied on each reboot. not a sticky root. I know my low post count will make you sketchy of this point. all I can say is that it is true. dropped it on my SD, used astro to access it, installed, and it worked just like blackrain, one click. except not sticky.
works great. gotta do it every boot.
Yep me to tried it and worked so how would this work on installing toms though since a reboot get rid of the root?
Oh my god i wanna do it. Its gotta be legit.. Right?
jachase42 said:
It worked, but unfortunately it has to be applied on each reboot. not a sticky root. I know my low post count will make you sketchy of this point. all I can say is that it is true. dropped it on my SD, used astro to access it, installed, and it worked just like blackrain, one click. except not sticky.
Click to expand...
Click to collapse
Well it got rooted, going to reboot and see
Hmmm. So if its not sticky, its pretty much pointless to me. Gonna way for the real Root to come. I mean the phone just came out so it shouldnt be long.
I'm still showing sudo permissions on reboot, going to test a few things. like the overclock app, and terminal access.
EDIT: Confirmed, SetCPU for Root cannot request permission. not a sticky root, just as it says.
so what does this do for me, i did it but i can't get into where all the apps i've downloaded are and stuff, i'm confused. what can i do with this root?
can you write to system from within android? if so root explorer will let you easily remove stock apps
no you can't due to current limitations
There is no rw for /system currently. < this should be written in bold and stickied.
I find their lack of information disturbing. If it really needs to be run every boot, why don't they say that? Their site doesn't have a single bit of info on it.
Well there is the long shell way.
Can I use this to create a perfect backup of my phone so I can restore it at any time?
actually when you do it on the phone it tells you that it needs to be run every reboot. so we can't get rid of sprint applications through the phone because of a lack RW for the system, but can we do this pc side???
i'm in boot mode what do i do so i can get rid of sprint apps and what not, how do i do a nandroid, and how can i back up all of my aps.
Anyone know what this means?
Root protip: bind mounts are your friend: busybox touch /data/local/blank; mount -o bind /data/local/blank /system/app/Sprint_NFL.apk
update (FIRERAT's implentation): http://forum.cyanogenmod.com/topic/2636-froyo-a2sdext/page__p__24386#entry24386
Ive seen this method around. And i was wondering....would it be possible to bypass the ADB steps for someone like me that doesnt have ADB access?
motoman234 said:
Ive seen this method around. And i was wondering....would it be possible to bypass the ADB steps for someone like me that doesnt have ADB access?
Click to expand...
Click to collapse
It's actually very easy:
Install Droid explorer (xda)
C:\Program Files\Droid Explorer\SDK\tools (Run... cmd)
I am trying this now...I will post back after installing some apps
EDIT= This is great and works a trea ...thanks dude
robuser007 said:
It's actually very easy:
Install Droid explorer (xda)
C:\Program Files\Droid Explorer\SDK\tools (Run... cmd)
Click to expand...
Click to collapse
Well thats my problem, my computer is super old and messed up. I cant get administrator access to downloads the proper files for adb. All i can do is download zip files to transfer for my phone lol.
motoman234 said:
Well thats my problem, my computer is super old and messed up. I cant get administrator access to downloads the proper files for adb. All i can do is download zip files to transfer for my phone lol.
Click to expand...
Click to collapse
Juts make another account and make it Admin. Then use the new account.
If your windows is that bad then I would either use a backup(if you did one) or a fresh install.
deuse said:
Juts make another account and make it Admin. Then use the new account.
If your windows is that bad then I would either use a backup(if you did one) or a fresh install.
Click to expand...
Click to collapse
Well to create a new account i would have to have admin access. Like a year or so ago this computer was givin to me for that reason lol. Theres a admin account on my computer but i cant get into it. Never could I wish there was a work around. Ive been messing with android for a long time and not once i have EVER used ADB lol. I would love to, theres so much stuff that i cant do because of this terrible computer.
motoman234 said:
Well to create a new account i would have to have admin access. Like a year or so ago this computer was givin to me for that reason lol. Theres a admin account on my computer but i cant get into it. Never could I wish there was a work around. Ive been messing with android for a long time and not once i have EVER used ADB lol. I would love to, theres so much stuff that i cant do because of this terrible computer.
Click to expand...
Click to collapse
Find yourself a copy of BartPE with Password Renew in it.
Burn, boot, use password renew to reset the password for any account.
I'm trying this, except when I get to "adb shell a2sd install" it says a2sd: not found.
:\
I had to go to /system/bin before i could run a2sd via ./a2sd, after which it worked.
What's the benefit of this over Froyo's SD implementation?
sleepwalkers said:
What's the benefit of this over Froyo's SD implementation?
Click to expand...
Click to collapse
it allows you to use the ext partition from previous versions of CM. Froyo's version now uses a fat32 partition on the sd card, therefore will not read the ext partition and the fact that your apps are on there.
sleepwalkers said:
What's the benefit of this over Froyo's SD implementation?
Click to expand...
Click to collapse
It's not as good, but coming from <= CM5 you may want to port along your apps.
Also Froyo's SD implementation is supported on an per app basis, but can be forced via CM. Note that dalvik cache is only moved to SD when using legacy a2sd.
sturmeh said:
It's not as good, but coming from <= CM5 you may want to port along your apps.
Also Froyo's SD implementation is supported on an per app basis, but can be forced via CM. Note that dalvik cache is only moved to SD when using legacy a2sd.
Click to expand...
Click to collapse
Not true.
See this thread for a more detailed discussion about the pros and cons between froyo2sd and app2sd.
http://forum.cyanogenmod.com/topic/2018-apps2sd-brainstorming/
I will have a try , Thanks..
LIKEHELL said:
I will have a try , Thanks..
Click to expand...
Click to collapse
froyo implementation isn't as good as apps2ext. The froyo method uses the fat32 partition but only if the dev of the app allows it to be moved to the sdcard. plus the apps don't all load on boot because the phone has to mount (prepare)the fat32 partition of the sdcard. This is the reason that many apps are not launching at boot like SetCpu and other root access apps, because the system boots before the sdcard is prepared. This is also the reason why many widgets and apps are missing from the app drawer for a lot of people as well. Cyanogenmod really needs to look at this and think about changing back to the old cm5 way of doing things.
I am trying to find a good backup app as doing a Nandroid did not work for me with doing aps2sd this way.
OMG
honestly , do you really need to add 5.1mb of crap to /system to get what should be a simple script running?
and what is /data/a2sd/Vending.apk for?
Awful, just awful
Code:
$ find
./a2sd-2.7-update3r1-signed.zip
./system
./system/lib
./system/lib/libext2_e2p.so
./system/lib/libext2_profile.so
./system/lib/libext2_com_err.so
./system/lib/libext2fs.so
./system/lib/libext2_blkid.so
./system/lib/libext2_uuid.so
./system/bin
./system/bin/fixa2sd
./system/bin/setupa2sd
./system/bin/apps2sd
./system/bin/boota2sd
./system/bin/chka2sd
./system/bin/reboot.a2sd
./system/bin/e2fsck_recvy
./system/bin/e2fsck
./system/bin/zipalign
./system/bin/aligna2sd
./system/bin/launcha2sd
./system/bin/bash
./system/bin/a2sd
./system/bin/starta2sd
./system/bin/busybox.a2sd
./system/etc
./system/etc/init.d
./system/etc/init.d/04apps2sd
./system/etc/init.d/00a2sdreset
./system/xbin
./system/xbin/apps2sd
./system/xbin/e2fsck
./system/xbin/a2sd
./data
./data/a2sd
./data/a2sd/Vending.apk
Firerat said:
OMG
honestly , do you really need to add 5.1mb of crap to /system to get what should be a simple script running?
and what is /data/a2sd/Vending.apk for?
Click to expand...
Click to collapse
Could you possibly implement something for this purpose and add your "all in one" script? Please
zimphishmonger said:
Could you possibly implement something for this purpose and add your "all in one" script? Please
Click to expand...
Click to collapse
seems I must, even if its not really needed
should have something soon
Firerat said:
seems I must, even if its not really needed
should have something soon
Click to expand...
Click to collapse
Thanks man!
Some of you may know me and some not. I was asked to help out on the SK4G development, so here I am.
I have some questions first.
1. You are using CWM?
2. Amend or Edify?
3. Do you have the drivers and adb set up yet?
Depending on the answers I can put out a couple of tests and then get to work on this.
I will need your newest deodexed framework-res.apk, twframework-res.apk, settings.apk, services.jar - and others as needed.
If you do not have a deodexed rom yet then I need a copy of your systemfs.rfs or a full odin to deodex it myself. I have the system dump, is this your newest rom? If so then I have already deodexed it - just let me know.
1. Yes, the epic 4g version which is buggy
2 don know
3.yes
Sent from my SGH-T839 using Tapatalk
1) No. It doesn't sound like the currently available CWM firmwares work well on the SK4G. I am waiting for one designed for this hardware. I have run CWM on other handsets, of course.
2) No. Had not heard of those until you'd mentioned them.
3) Yes. Working well. We're all set here, at least.
System dump: There only seems to be one ROM/firmware version for this phone so far. The one you have should be current. I pulled mine in this thread:
http://forum.xda-developers.com/showthread.php?t=1037403&page=5
Specifically here:
http://forum.xda-developers.com/showpost.php?p=13210149&postcount=59
I'm happy to help further. Please simply let me know what you need.
And thanks for taking this on! This could be a solid phone without some of the bloatware trash foisted on it.
1. They are using the one click root for the epic by noobnl which installs CWM 2.5.1.0
2. Amend though can't you just use update-binary and make it compatible with both
blu9987 said:
1. They are using the one click root for the epic by noobnl which installs CWM 2.5.1.0
2. Amend though can't you just use update-binary and make it compatible with both
Click to expand...
Click to collapse
Yes, but I am old school and still use amend most of the time and needed to make sure it was going to be compatible.
Once I see some feedback on the theme I posted I will move forward - I just need to know how it turns out so I will have a better understanding of the phones layout.
Might need to send Koush a message and see if we can get a proper recovery going.
I really would love it if this phone got some custom roms. I don't want to get rid of it. But I put a ad up on craigslist to trade for a mytouch 4g.
Sent from my SGH-T839 using XDA App
Also as far a getting a proper working recovery, i think we may need a recovery that supports the ext-SD card. our internal memory isnt used by us because its so small. its used for things like installing apps i believe. if you use a file manager you'll see the only available SD card is the external one and same when mounting the phone. i think the epic and vibrant recovery would work just fine except we'd need one that supports the external SD card.
there is a kernel called dead horse that i used on my vibrant that had this support for ext SD but i dont think theres a way to get just the recovery out of it. hopefully someone might know a way to direct CWM to our ext SD then we might be on to something ..
ayoteddy said:
Also as far a getting a proper working recovery, i think we may need a recovery that supports the ext-SD card. our internal memory isnt used by us because its so small. its used for things like installing apps i believe. if you use a file manager you'll see the only available SD card is the external one and same when mounting the phone. i think the epic and vibrant recovery would work just fine except we'd need one that supports the external SD card.
there is a kernel called dead horse that i used on my vibrant that had this support for ext SD but i dont think theres a way to get just the recovery out of it. hopefully someone might know a way to direct CWM to our ext SD then we might be on to something ..
Click to expand...
Click to collapse
Its just a driver issue. We need to know exactly which SD card reader is in the phone and see if we can contact the manufacturer for the source.
I do not know how to decompile things like drivers, but I would like to know so I could get the ball rolling on this.
I'd love to see development pickup on this phone.
I've had my G1 since Dec 08 and happily rooted and did whatever I wanted to do it with the huge support from the developer community that the G1 received.
I'm keeping myself stock until someone gets Clockwork working with nandroid and there's an unroot method.
d4n137_91 said:
I'd love to see development pickup on this phone.
I've had my G1 since Dec 08 and happily rooted and did whatever I wanted to do it with the huge support from the developer community that the G1 received.
I'm keeping myself stock until someone gets Clockwork working with nandroid and there's an unroot method.
Click to expand...
Click to collapse
I feel the exact same way. I just picked mine up today and I really want to dive into it.
Yeah man, id like to see some development for this phone. I'm willing to help with whatever. This forum seems very dead though. Let's hope it picks up.
Sent from my Sidekick 4G using XDA app
what is the sdcard mounted as? mmcblk0p1? mmcblk1p1? This is key to getting recovery set up.
Where do I find that? I just rooted the phone but I haven't flashed the buggy recovery image
Sent from my little sidekick
gearhead27 said:
Where do I find that? I just rooted the phone but I haven't flashed the buggy recovery image
Sent from my little sidekick
Click to expand...
Click to collapse
adb shell
cd sys
cd block
ls
pastebin that info
that should tell me what I need to know
ive got it. it's mmcblk0p1
Same as the Vibrant, but theirs is mounted to internal sd. I would just need to switch up some stuff.
1st and foremost.... I need your guy's initramfs from your kernel
Idk too much about the initramfs nor how to extract it.
If I'm right the zImage is the kernel maybe this could help you so I've uploaded it to dropbox aswell.
http://db.tt/hhJIGXn
If it needs to be done from our phone could you point us in the right direction on how to get the initramfs.
Sent from my SGH-T839 using XDA App
So exciting seeing the development picking up
so happy to have someone look in this 4rum......im willing to help,,,,,if you guys need someone to be a tester.....just let me know....
ayoteddy said:
Idk too much about the initramfs nor how to extract it.
If I'm right the zImage is the kernel maybe this could help you so I've uploaded it to dropbox aswell.
http://db.tt/hhJIGXn
If it needs to be done from our phone could you point us in the right direction on how to get the initramfs.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Thanks, I'll get you guys something to test with tomorrow night when I get to work.
krylon360 said:
Thanks, I'll get you guys something to test with tomorrow night when I get to work.
Click to expand...
Click to collapse
can't wait to test it.....thanks a lot
If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.
was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.
The zip file seems to be corrupt. Could you re-upload plz
worked great on my end, no problems.
khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .
wow this method really blaze hellfire much thanks to your( you) & (rom dev)
Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .
thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid
dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA
Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium
It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.
Google Wallet Installer for Verizon, AT&T, T-Mobile, and US Cellular Samsung Galaxy S3.
Requires ROOT, an UNLOCKED BOOTLOADER, and BUSYBOX!(A deodexed ROM is just recommended)
My newest project, RemoteFlash, was just released! Take a look and give it a try!
Wallet Installer Is Now Available For Free To All Supported Carrier Models On XDA! (Donations Appreciated)
My application, "Wallet Installer", will install Google Wallet on almost any US based Samsung Galaxy S3. It simply edits your build.prop and then places the correct modifications into your system. It downloads all the files from my personal server, which is pretty quick. Just select the appropriate Rom type: AOSP, JB Touchwiz, or ICS TouchWiz, and then your carrier: Verizon, AT&T, T-Mobile, or US Cellular. I also added a restore option for your build.prop, so you can restore it after you setup Google Wallet. Hopefully this helps you out and makes the process easier!
Wallet Installer has been updated on the server side. The credit goes to Paul Obrien for the new version! To install it, simply reset Google Wallet, delete it, and then rerun Wallet Installer! Make sure to also have BusyBox installed/updated!
Please donate if my work helps you : )
V3: No Recovery/More Stable
And as always: I take no responsibility for bricked devices, whether a soft brick or a full on brand new coffee coaster.
Dude. You are awesome. I was just in the official wallet thread and was hesitant on going through with it because it seemed daunting having to change the build prop. I'm about to flash slim Bean 3.1 and then try this out. Will update this post once I finish trying it out . Hopefully all goes well!!!
Well I ended up lagging on the install but just wanna say thanks again because it worked perfectly. First try and not a single problem as of yet. Awesome!!
Glad to help! Hopefully all goes well! If the download stalls just give it a while, my server is a retired galaxy nexus hooked up to WiFi lol. My WiFi sucks sometimes.
Internal SDcard Corrupt?
Prl91 said:
Google Wallet Installer for Verizon Samsung Galaxy S 3's(d2vzw)
My application, "WalletInstaller", will install Google Wallet on any Verizon S3. It simply swaps out your build.prop with a modified one and then flashes an open recovery (TWRP 2), and in the open recovery flashes the latest version of Google Wallet along with the required NFC libs for your rom. It downloads all the files from my personal server, which can be somewhat slow, but I'll be upgrading soon. Hopefully there won't be any download issues. Just select the appropriate rom type: AOSP, JB Touchwiz, or ICS TouchWiz. Hopefully it helps you out and makes the process easier! It has been tested on my device, which is running CM10, but the other options haven't been tested, but they should work great. I will also hopefully make it to support all US carrier based S3's after the weekend is over.
My application will be in the market for 99 cents if you feel like supporting the cause(will post link once uploaded), or you can download it here for free. Please don't post links to my application without my personal consent. Thank you!
And as always: I take no responsibilty for bricked devices, whether a soft brick or a full on brand new coffee coaster.
Click to expand...
Click to collapse
So I installed the app and set it all up just fine, in fact, I was about to test out wallet at a locat establishment but I noticed something was a little weird. I tried to change my wallpaper to a picture in my gallery. For some reason I got an error that "Not enough space. Delete photos, music, etc." Last time I checked I had plenty of space. I opened up setting and storage to find my device storage has a total of 4GB of space (with close to 2GB's of free space remaining). My S3 is a 16GB unit. Obviously things are a bit haywire. I'm running CleanROM 5.0 at the moment so I'm not sure if your app would conflict with that but things were fine prior to this. What do you think?
when i choose ics touchwiz install it loads terminal emulator and says rm failed for /system/build.prop no such file or directory
I'm not sure if my app would interfere quite like that. It shouldn't, but when messing with the build.prop and a custom ROM you can never be positive. If anything else odd happens, pm me and I'll look into it.
brusslesprouts said:
when i choose ics touchwiz install it loads terminal emulator and says rm failed for /system/build.prop no such file or directory
Click to expand...
Click to collapse
It's possible that your system didn't mount properly, or that your ROM is using some sort of mod that moved the build.prop, or it may have been removed or altered by another application.
Got mine installed and all looks good but same thing about the wallpaper..........says no space even though it has space.
Ronin09 said:
Got mine installed and all looks good but same thing about the wallpaper..........says no space even though it has space.
Click to expand...
Click to collapse
That's odd. What ROM type are you running?
CleanROM 5 also
I mean it installed great. I even put a new debit card on it. Going to try it out in just a hour or so but no space when using the gallery to change wallpaper
Ronin09 said:
CleanROM 5 also
I mean it installed great. I even put a new debit card on it. Going to try it out in just a hour or so but no space when using the gallery to change wallpaper
Click to expand...
Click to collapse
Maybe it's just an issue with CleanRom. Still really weird though. I won't know til more people give it a shot. Anyways, let me know if wallet works! Thanks for trying it.
Hope your bugs get worked out I'll gladly buy/donate to this app
Sent from my SCH-I535 using xda premium
Hulk0069 said:
Hope your bugs get worked out I'll gladly buy/donate to this app
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks Hulk! I'm sure I can get it all ironed out, it'll just take some time ; )
Same wallpaper issue. Also now I cannot access internal sd card via root explorer.
Sent from my Galaxy Nexus using xda app-developers app
Same here, I can't access Internal Card........if not a fix soon, I will probably have to redo flash of ROM and just wait for better wallet. This worked too btw
---------- Post added at 07:50 AM ---------- Previous post was at 07:08 AM ----------
Here's one question for you...
Why does your installation include TWRP 2.3.1.0.
I already had a CWM Recovery...that was strange to me.....when I get to work I am going to try to flash over that to see if that's the problem. Could be that. But right now I can't access my internal drive let alone the backups if I were to start over.......LOL.....I wouldn't be able to get to.
Live and Learn I guess.
Ronin09 said:
Same here, I can't access Internal Card........if not a fix soon, I will probably have to redo flash of ROM and just wait for better wallet. This worked too btw
---------- Post added at 07:50 AM ---------- Previous post was at 07:08 AM ----------
Here's one question for you...
Why does your installation include TWRP 2.3.1.0.
I already had a CWM Recovery...that was strange to me.....when I get to work I am going to try to flash over that to see if that's the problem. Could be that. But right now I can't access my internal drive let alone the backups if I were to start over.......LOL.....I wouldn't be able to get to.
Live and Learn I guess.
Click to expand...
Click to collapse
I'm sorry that you're having trouble. I included TWRP because it uses an open, unencrypted script file to pass commands to recovery. CWM, from my understanding, requires an encrypted, not so universal script file called extended commands. Depending on what recovery someone was running, flashing a script would not work, or it would possibly brick their device. I wanted to make sure everything was done correctly.
Also... I will take a look at all my server side files today and the app. I can't make changes from where I am, since I don't have ftp setup and I'm out of town, but I can download them and see where I may have gone wrong. My best guess is the build.prop swap causing issues, if any of you have possible leads, post them here and I can attempt a fix later today or tomorrow.
BTW...Wallet worked like a charm in 7-11 and Whole Foods
Taking pictures is a little harder too...have to switch to external to save the pictures....the Camera 4.2 doesn't even allow you to switch to external card.
Would be a shame to scrap this working wallet for these issues
Ronin09 said:
BTW...Wallet worked like a charm in 7-11 and Whole Foods
Taking pictures is a little harder too...have to switch to external to save the pictures....the Camera 4.2 doesn't even allow you to switch to external card.
Would be a shame to scrap this working wallet for these issues
Click to expand...
Click to collapse
I'm getting ready to attempt a flash on CleanRom in a few minutes to see if that's the only ROM having issues. Hopefully you guys can stick this out until everything's working great ; )
I flashed wallet and libs using my app on CleanRom 5. I was able to replicate the same error as you guys posted. Also, I don't know if you guys checked, but in recovery it mounts the internal sdcard perfectly, so that tells me it may have something to do with CleanRom in specific. I'm going to flash through some stock touchwiz ROMs with Odin and see what results I get in that area. Hopefully it's just a ROM specific ordeal. Sorry for the long posts, just trying to keep you all updated!