Database Users

SU/Root gone on ADP1 running JFv1.50 ADP1.5? [Solved?]

Hey all. I have searched but I was unable to find a thread pertaining this issue.
Phone: Android Dev Phone 1
Running: JFv1.50 ADP1.5
What has happened is that today SU/Root seemingly stopped working. I discovered it when I bought Kosh's Screenshot app and started it up. The app requires SU permission, and therefore the "SU Request" window popped up. But it's blank. A blank black screen which eventually will run low on memory and then force close.
I then tried to open the Superuser Permission app, same result. Opened Task Manager for Root Users, same deal. Opened the Terminal Emulator and typed "su", which actually worked! I still had SU privs there. Closed the TE and decided to reboot the phone, and now I don't have SU privs in TE anymore. Everything that's non root related is still working fine.
Does anyone have an idea what's happening here? I suspect that maybe the Market Enabler app or the AdsFree apps could have something to do with it, because they're the only root related apps I have installed the last few weeks, before this problem occurred.
I'm sure a wipe would fix this glitch, but I'd prefer not to do that unless it's necessary. Plus, it would be nice to know what's causing this, so I can avoid it in the future.

Same thing has happened to me. It worked fine for Term Emu, task manager, and ad block. But I tried using an OC app and when super user popped up blank. All my previous apps still work but any new root apps I install do not work. Not sure why though and the only way I found to fix it is to wipe. Do you have your apps on the sd card? I'm using the old method haven't gotten around to trying the new method. Not sure if that is the issue or not, the old version of super user never gave me any issues.

I did a wipe, and it sorted the problem out, for some root apps. Now I'm back to the same crap again though, the SU Request window pops up but it's all black and eventually it force closes.
According JF's blog he included "a much better Superuser app, courtesy of zinx" in the 1.50 release. It's obviously what's causeing our problems, I never had an issue with the old one, but I don't know what to do about it. I don't want to go back to 1.1 or Haykuro's builds. I guess I'm stuck with a semi-crippled JFv1.50 ADP1.5 until someone with more brains than me finds and posts a proper solution.

Yeah Ive been noticing the same thing. Also the superuser list GUI is horrible. I liked how in the last one you can choose what programs you'd want to remove su access from.

andonnguyen said:
Yeah Ive been noticing the same thing. Also the superuser list GUI is horrible. I liked how in the last one you can choose what programs you'd want to remove su access from.
Click to expand...
Click to collapse
Exactly. I'm not sure what he means by "a much better Superuser app", because for a layman like myself it seems a lot worse than the old one

This is just going from bad to worse. Now I discovered I have no positioning via wifi/3G anymore. I have to start the GPS and go outside and wait for a signal to get a lock on my position, which sucks. What the hell is going on? If not even a wipe is enough I guess I'm looking at a complete reinstall, but if all this has happened once it can/will happen again. I would much prefer to find the cause of all this crap.

Ok, so I found the cause for the Assisted GPS issue at least. My Micro SD card needed repairs. I put it in a SD card adapter and plugged it in to my laptop and let Vista repair the file system (apparently there were close to 100 errors on the damn thing) and now it seems to be working again.
Edit: This might actually have fixed my issues with the superuser permissions too. Knock on wood. I'll have to get back to you on this.

I'm having this Exact issue
I am having this exact same issue on dudes build. I have tried everything from scanning to formatting the SD i have flashed back and forth from Jf1.42 to jf1.50 and then to all different dude builds and i have no clue what to do next.
I do a wipe every time i flash and the only way to get any su access is to have jf1.42 or haykuro build. Anyone Else having an issue? I have been working on this for 3 days straight now...

For me it was an SD card issue. If you have a spare card, try that instead, or if you can borrow a card from a friend, just to see if it resolves your problems.
I realize that you have repaired/formatted your SD card, but it could be something wrong with it that screws things up. Worth a try, right?

Absolutely I'm looking for one right now thanks for the quick response. I'll let you know if it works. I have a 2gb sandisk in there now, so i still have my 1gb and my girlfriends 1gb too. Her phone has no su problems at all.

I also ran across the same problem reported here, only a wipe solved it. I believe it had something to do with the Market Enabler (non-signed) app, which was the only one I installed that first showed me the dreadful empty SU screen...

Fixed It
My Problem has been fixed by formatting the sd card with the phone itself.
I copied off all my info, unmounted it from the computer, unmounted it from the phone, this gave the option to format the sd card.
Once that was done i copied all my data back and when i installed programs from my sd i have not had a single su problem since.

I was having all these same problems in JF's 1.5 build, and none of the wiping/formatting SD/trying a different SD card combinations did the trick. Then, I went into JF's blog post where he released 1.5, and someone posted there that enabling USB debugging would fix the issue. I did this, and what do you know, now my superuser permissions app works again in everything, even in unsigned apps! Maybe this is why a wipe fixed it for some people, and not for others?

n17ikh said:
Then, I went into JF's blog post where he released 1.5, and someone posted there that enabling USB debugging would fix the issue. I did this, and what do you know, now my superuser permissions app works again in everything, even in unsigned apps! Maybe this is why a wipe fixed it for some people, and not for others?
Click to expand...
Click to collapse
Not to Jesus resurrect this thread, but I had the same issue and same fix as n17ikh here on the ION build. Enabled USB debugging and su/superuser permissions started working Too bad I have to disable USB debugging in order for my car stereo to mount my G1 as a USB device, but at least I have a solution
Hope this helps anyone else who may stumble upon this.

Some Questions Before I Root

I've considered rooting and installing a custom ROM dozens of times ever since I got my Droid X back in August and I've finally decided I'm just going to do it, but i just want to double check a few things before I root my phone and install Fission:
1. I know that rooting voids your warranty, but if I have problems with my phone and I end up needing repairs, can I just unroot my phone back to stock and still have my phone be covered under the warranty?
2. Will my phone be secure rooted with a custom ROM? I don't want people having access to my personal info contact data, and my passwords.
3. If I Overclock to say 1.2 or 1.3 Ghz with ULV, will I have stability problems with demanding 3D games or other demanding apps?
4. After I root and install my Custom Rom, will I need to reactivate my phone or need to re-add my phone contacts/apps?
5. Will Z4Root work on system version 2.3.340?

I have unrooted and exchanged under warranty with no problems. Your phone will be just as secure. 1.2-1.3 are very stable on my phone. If you do have to reactivate it's as easy as dialing *228 and following the prompts. If your contacts are "google" contacts they'll return to your phonebook. Your apps from the market shall return without a problem. And yes, z4root will work with your system version.
Sent from my DROIDX using Tapatalk

I am having difficulty rooting my droid x. I am an android noob, but am a pretty savvy user. I used z4 (permanant) and it says it has been rooted when i launch the app. However i see no appreciable difference in access. My terminal still shows a $ prompt and i cannot uninstall verizons crapware. I used rage against the cage prior to z4 with similar results, but i was able to at least get temporary su access and install the bootstrap recovery and perform a system level backup. It reverted to user access after rebooting. Please help.

Superuser confirmation
alright, if you want super user privileges in terminal type "su", then once you hit enter, you get "#" instead of "$" To test if you have root access, first check app drawer for "Superuser" if its there, open an app that requires it, (wifi teather, root explorer, rom manager to name a few) you should get a pop up similar to this
http://www.google.com/imgres?imgurl...=1&ndsp=12&ved=1t:429,r:8,s:0&biw=888&bih=638
that would be a diffinitive confirmation that you have superuser permissions.
The way I remove verizons crap once rooted, is to use root explorer, go to system/app and find the .apk files you want to remove. There are lists around the forums what is safe to remove. I highly recommend simply renaming the files. For example, the 3g hotspot app is called mynet.apk, so I would just rename it to mynet.bak, or mynet.apk.bak, really anything that lets you know what it is, but removes the .apk extension.

Ok, I have confirmed su access, but am unable to rename any of the offending .apk's. I am simply told that the operation was unsuccessful. I have tried a couple of different file managers, as well as trying from a terminal, still no luck. I like 2.2.1 alright, but if i can't control what apps are running on my phone with root access, I may want another ROM. Any suggestions are appreciated, aswell as any links to a rom installer that is pc-less.

I usually rename apk's from Root Explorer, just prefer the graphical interface, so I can't really help you on the terminal process.
Rom manager is "pc-less" although most roms are posted in forums first it is often the easiest route, also lets you make backups and restore. There are a few posts around on how to install a rom you might want to read first. Also, you should find the thread for the rom before you flash it, in favor of size and speed, some developers go down to bare minimum and may remove something you need/want.
I have not used it, but I hear Titanium Backup allows you to "Freeze" apps, so that is a possible route also.
2.2.1 is not exclusive to people running official vzw builds, many of the roms on the forum (and rom manager) are running 2.2.1, so you will not be taking a step back to an earlier release.

SharkBaitDave said:
I usually rename apk's from Root Explorer, just prefer the graphical interface, so I can't really help you on the terminal process.
Rom manager is "pc-less" although most roms are posted in forums first it is often the easiest route, also lets you make backups and restore. There are a few posts around on how to install a rom you might want to read first. Also, you should find the thread for the rom before you flash it, in favor of size and speed, some developers go down to bare minimum and may remove something you need/want.
I have not used it, but I hear Titanium Backup allows you to "Freeze" apps, so that is a possible route also.
2.2.1 is not exclusive to people running official vzw builds, many of the roms on the forum (and rom manager) are running 2.2.1, so you will not be taking a step back to an earlier release.
Click to expand...
Click to collapse
If you are trying to rename apps in the /system/app portion of the OS, you will need to mount /system as RW first.
from terminal: mount -o rw,remount /dev/block/mtdblock4 /system
After it has been mounted read-write, you should be able to rename...
to remount as read-only: mount -o ro,remount /dev/block/mtdblock4 /system

zwade01 said:
I have unrooted and exchanged under warranty with no problems. Your phone will be just as secure. 1.2-1.3 are very stable on my phone. If you do have to reactivate it's as easy as dialing *228 and following the prompts. If your contacts are "google" contacts they'll return to your phonebook. Your apps from the market shall return without a problem. And yes, z4root will work with your system version.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Just out of curiosity, did you (or anyone else for that matter) have to reactivate your phone after rooting and installing a custom ROM? I'd rather not have to re-activate my phone every time I want to update a ROM or change to a different ROM.

Thank all of you for the great info. Here's what I've learned after a day of rooting and romming: titanium freezes apps only in the paid version, z4 was the most user friendly app for rooting noobs, milestone overclock works well if you have the patience to lock up your phone several times finding the right settings, and I'm digging apeX 1.3.1. Thx to everyone for your help, i will definately be checking here frequently. One last question: where might i find a side by side comparo of roms with things like features and memory footprint, etc.? Or am I asking for too much. Im not scared of the search button, but i will defer to the more experienced of you. Thanks again.

galaga4991 said:
Thank you for your response. Just out of curiosity, did you (or anyone else for that matter) have to reactivate your phone after rooting and installing a custom ROM? I'd rather not have to re-activate my phone every time I want to update a ROM or change to a different ROM.
Click to expand...
Click to collapse
I used rom manager to load apeX 1.3.1 and did not need to #228. I did not clear the user data or cache, but I do not know if that affected my results or not. Your mileage may vary.

stpvapor said:
Thank all of you for the great info. Here's what I've learned after a day of rooting and romming: titanium freezes apps only in the paid version, z4 was the most user friendly app for rooting noobs, milestone overclock works well if you have the patience to lock up your phone several times finding the right settings, and I'm digging apeX 1.3.1. Thx to everyone for your help, i will definately be checking here frequently. One last question: where might i find a side by side comparo of roms with things like features and memory footprint, etc.? Or am I asking for too much. Im not scared of the search button, but i will defer to the more experienced of you. Thanks again.
Click to expand...
Click to collapse
I don't know that anyone has really done a side by side per say. Since you say you are apeX, then if you are looking for more ROM's that contain blur features, then I would recommend looking into ZapX Bazinga, or Fusion (from the same creator as Fission, but just with blur). I have not worked with any of the Blur ROM's so far...
If you are looking for ROM's that do not have blur, then the big ones are Liberty, Fission 2.5.7, GummyJar 2.5, and Rubix Focused 1.9.5. Liberty is the big one right now, because it just came out and combines the great talents of Kejar31 and Jrummy. Most others I believe are using Fission. All are great choices, as the dev's do some AMAZING work.
Each has their owns unique feel...so I woudl recommend just digging through each thread for their respective ROM's as they usually include what components are built into each ROM on the original post of each thread.
Hope this helps somewhat =)

another ROM to try is DarkSlide. It comes in both flavors, Blurred & Blurless. It's fast, stable & well supported. You only have to re-activate if you wind up bricking your phone & have to flash an SBF. My advice it to spend the $$ on DroidXBootstrapper (available in the market) to make a nandroid backup prior to flashing your new ROM. This way you have a base to go back to in the event you run into problems, or want to try multiple ROMS. One other suggestion is to rename each backup into something that will let you know what the backup actually is, like StockROMBU or the like.

Archos 101 one-click-root for firmware 2.0.71 using Archangel

Download rar file with apk:
dump.ru/file/5037798
or
depositfiles.com/files/7sh8g638s
rar password: cea69e0419
sha1sum of apk: 80ff2925e12b8d3f2e9c0cabd5b294e6556b2e3f
Archangel one-click-root from the Archaism Team
This will give you temporary or permanent root on your Archos 101 - firmware 2.0.71
Archos are kind enough to provide a SDE firmware which can allow root access,
but involves some significant changes to the system and they say that they will
invalidate your warranty if you install it. This is a bit frightening for new owners.
Archangel solves this with a painless one-click-root which you can uninstall at any time.
It does not use the SDE developer firmware.
This was specifically designed for the Archos 101 with firmware 2.0.71 - it may work on
other Archos devices or firmwares, but has not been tested and is not recommended for them.
If you find this application useful, please donate to those great forums who have given
the android root community so much. Encourage them to keep up their great work. We are
fans of C-Skills Blog, XDA Developers and Modaco Forum.
When installed, this app will use approx 10mb of storage space. Don't run it if you don't
have that much spare.
Usage Instructions:
1) Make sure you have 10mb of space available on the internal storage
2) Make sure you are connected on Wifi
3) Run the Archangel app
4) Click to install SuperUser application
5) Click to get root!
6) Check everything is working correctly, try an app which needs root
7) Once you have root you can tick the "Permanent" root option to always have root.
8) Party Hard!
To turn off root, either just reboot, or turn off permanent root and reboot if you had
enabled it.
To uninstall, just uninstall like any other app. You may also want to use the menu item
to clean up before you uninstall.
You can create a script in /sdcard/sdcard/extraroot.sh and this will be executed as root
whenver you reboot, so you can use this to do any additional root functions you want.
Enjoy!

does this work?
anyone try yet?
I have A70 so i'm not sure if this will work for me
ohh a video demo would be nice

I think this is a scam "Permanent" root is not possible because the filesystem is a read-only filesystem. But I can be wrong.
I'll download this and try to inspect it.

I hope this works, I really want to get Titanium Backup working.

Well I haven't tried yet, but did a quick analysis on the APK:
Permissions on the APK does not seem to be too fishy:
Storage: modify/delete SD card contents
System tools: view and change WIFI state
and automatically start at boot
APK contains superuser, su and ls binaries.

It Works
jsperri: I saw the same as you when I looked at it.
I did install it and it seems to be working. I was able to go su from the terminal and backup an app with Titanium Backup.
I can also confirm that if permanent root is checked this will still work after reboot. When I was looking at the app it looked like it plugged into the launcher process. So perhaps it is just starting just after android is loaded.
Although I have not verified, I suspect that /system is still read only because of squashfs.

What bothers me is first the dates within the apk are 29/2/2008 for all files.
Then the binaries su is a gzipped binary superuser is a gzipped superuser.apk BUT ls is not compressed.
Why do they need ls the ls of the ROM should work fine. I suspect a trojan but i'm not sure. I could be paranoid but a rar with passwords come on......

xdaAlan said:
jsperri: I saw the same as you when I looked at it.
I did install it and it seems to be working. I was able to go su from the terminal and backup an app with Titanium Backup.
I can also confirm that if permanent root is checked this will still work after reboot. When I was looking at the app it looked like it plugged into the launcher process. So perhaps it is just starting just after android is loaded.
Although I have not verified, I suspect that /system is still read only because of squashfs.
Click to expand...
Click to collapse
So xdaAlan your first post and you claim it works and what proof you can give us? screenshots maybe.....

I agree with extreme caution on files coming from the "wild" (my apologies to archaism1).
Permissions on the APK seems to be reasonably OK.
Like wdl1908 I was also puzzled about the files dates and the presence of ls binary.
Well, I'll run this Archangel beast on a resetted tablet and report here the results with proofs

The ls binary is definitely fishy I reexamined the rar file and the file dates for the readme.txt and the apk are 18/8/2009 whats up with that.......

jsperri said:
I agree with extreme caution on files coming from the "wild" (my apologies to archaism1).
Permissions on the APK seems to be reasonably OK.
Like wdl1908 I was also puzzled about the files dates and the presence of ls binary.
Well, I'll run this Archangel beast on a resetted tablet and report here the results with proofs
Click to expand...
Click to collapse
Thxs jsperri I don't have a spare unit and don't really want to reset my unit.

Does not seem to be doing much on my A32 test machine.
Just tested on my 70H, no root either ;(
What the application does is:
- install superuser apk
- does something while it says "please wait"
(ps on adb shell shows a
Code:
/tmp/ls 0x62c7a315 0x260de680
so ls may well be part of the exploit)
There is a checkbox "Permanent root" that probably just starts Archangel program on boot
(this is just my guess, based on the APK permission, and the fact there is little chance that the squashfs gets written)
Well, I'm pausing my investigation here, waiting for others feedback, hopefully positive.
There is a screenshot of the application here along with a comment from a user saying it worked on an Archos 70 IT.

hi,
i haven't been very careful about trojan risks, but i installed it on my 70it and it works!
how can i know if a trojan is instaled?

toutiwai said:
hi,
i haven't been very careful about trojan risks, but i installed it on my 70it and it works!
how can i know if a trojan is instaled?
Click to expand...
Click to collapse
Was WIFI enabled ?
How long does it take after the button says "Please wait" ?
What's next step on screen ?
Regarding the trojan risk, it's hard to say, you'd eventually want to run tcpdump to log for internet traffic on the tablet when the program is running. Also check if there are programs left (appart from Superuser) after uninstalling Archangel.

note: after install, i didn't asked to be "permanent root", but it launches "archangel" at startup anyway (but no root if i don't ask for)
wifi enabled: yes, enabled AND connected, if not it can't get "root"
how long? if wifi connected, say... 15-25 sec...
next step: nothing, the button "install root" changes in "i'm root" or something like this...
note: i had "superuser" already installed (but not rooted) before installing archangel, so it didn't asked me to install superuser
i'll try to be more precise next time if important...

archaism1,
Can you please give us some details on Archangel program, how the exploit works, why is Wifi necessary ? It would be great to trust this new tool, but it's difficult without having more details on a program coming from a dump archive and not a very well know author...
archaism1 said:
....
Archangel one-click-root from the Archaism Team
This will give you temporary or permanent root on your Archos 101 - firmware 2.0.71
Archos are kind enough to provide a SDE firmware which can allow root access,
but involves some significant changes to the system and they say that they will
invalidate your warranty if you install it. This is a bit frightening for new owners.
Archangel solves this with a painless one-click-root which you can uninstall at any time. It does not use the SDE developer firmware.
...
Click to expand...
Click to collapse

Will this work on my archos 43 Internet tablet ? Anyone brave to test and report.

http://www.appbrain.com/app/root-checker/com.joeykrim.rootcheck
anyone tried root-checker after trying this "1-click-root"? to check that it does what it claims?
I'd love to believe this, but i'm naturally sceptical.

i just tried (archos 70IT), and "rootchek" says it's ok

well at least that is promising , thanks

Known App Conflicts Causing Problems with Xoom

I hope that this thread can be pinned so that we can all be warned about serious conflicts with app updates and versions and some of the kernels and roms we have flashed. Still hoping this thread will be used for solid advice. Please contribute.
Some of these apps/versions are consistently causing problems, including near-bricks.
My first warning is for Xoomers to avoid updating to the 4.XXX version of Clockwork Recovery. This version doesn't "see" our external sdcard, and backs up to the internal sd, and also, prevents flashing from the external sdcard...if you have already updated through Clockwork Mod Rom Manager, you will need to re-flash a good recovery.
Update 6/21-- This is still a problem--do not update to Version 4.XXX of Clockwork Mod Recovery through ROM Manager. If you did, then in RM, scroll to the bottom and flash an older recovery (2.0.2.5 I think) then the newest one pinned to the top of solarnz's thread in the development section.
There have also been problems with the updated busybox and with the binaries that the updated superuser app installs.
Please, can we get more definitive statuses on these two applications?
Please use this thread and add in your own known problem apps, etc. and if possible suggest or link to solutions for others who may be ensnared in these conflicts.

Okantomi is right. This thread should be pinned. I have seen at least a dozen cries for help on Q&A from people that have fallen into these two traps.

cam30era said:
Okantomi is right. This thread should be pinned. I have seen at least a dozen cries for help on Q&A from people that have fallen into these two traps.
Click to expand...
Click to collapse
Thanks cam30era, you have been one of the people giving the warnings as well.
OK this is a shameless bump to keep the thread visible.
Oh yes, and never flash a .zip file through adb!!!

ROM manager causes so many problems. I don't see the point of it.

kev0153 said:
ROM manager causes so many problems. I don't see the point of it.
Click to expand...
Click to collapse
It's actually a very useful app in so many ways, but there should be more coordination between the developers...it seems the 4.XXX update sort of treats the Xoom like a phone with only a small internal memory and an external sd card being the only thing called sdcard.
On a tablet, however, we have a large internal sdcard (32GB on Xoom) and mounted to that is our external sdcard (this mount point is one of the reasons that Google is hesitant to OK the external SDcard on tablets--makes for an awkward file structure, I guess). This version of CWM seems to only see our internal sdcard on the root directory and treats it as the external sd.
If this explanation is wrong, those with more knowledge please correct me. I think it's helpful for people to know, in layman's terms, what's going wrong, as it can help them use logic to avoid problems in the future, but I don't want to spread mis-information!

What's wrong with the latest "Superuser" and "Busybox", though?

kcrudup said:
What's wrong with the latest "Superuser" and "Busybox", though?
Click to expand...
Click to collapse
I think these are either in conflict with the Tiamat ROM 1.0 /and or newest updates missing files (busybox). This was recorded in an ongoing discussion in development (dinomight OP) and I fell victim to updating to a conflicting busybox version. All was fine until I rebooted and stared the dreaded RSD 3 in the face. God only knows how I made it back from the edge...

okantomi said:
I think these are either in conflict with the Tiamat ROM 1.0 /and or newest updates missing files (busybox). This was recorded in an ongoing discussion in development (dinomight OP) and I fell victim to updating to a conflicting busybox version. All was fine until I rebooted and stared the dreaded RSD 3 in the face. God only knows how I made it back from the edge...
Click to expand...
Click to collapse
I installed busybox from the market too, is it safe to uninstall? I was trying to get cifs to work somehow and I ended up installing busy box. The xoom froze and I got the RSD 3 somehow. I kept smashing button combinations until it rebooted. It has been fine ever since.

Kippui said:
I installed busybox from the market too, is it safe to uninstall? I was trying to get cifs to work somehow and I ended up installing busy box. The xoom froze and I got the RSD 3 somehow. I kept smashing button combinations until it rebooted. It has been fine ever since.
Click to expand...
Click to collapse
Wow! Glad you were able to recover! I think that solarnz made a stable version and I think it's in the development section inhis recovery thread.

kcrudup said:
What's wrong with the latest "Superuser" and "Busybox", though?
Click to expand...
Click to collapse
Long story short :
The busybox wasn't compiled with run-parts. In our rom, the ramdisk used to rely on this for init.d. This has been fixed.
With superuser, the su binary appears to be incompatible. I haven't had a look at this issue yet.

solarnz said:
Long story short :
The busybox wasn't compiled with run-parts. In our rom, the ramdisk used to rely on this for init.d. This has been fixed.
With superuser, the su binary appears to be incompatible. I haven't had a look at this issue yet.
Click to expand...
Click to collapse
Thank you solarnz. So is the busybox in the market safe to install/update or do you have a link to the fixed version?

As long as you have flashed the rom update 3, you can flash busybox without worrying.

issues with swype - eh09 pwgb v. 2.0b3 - please help!!

I am currently running powerwashed gb v 2.0 beta3. It has the stock version of swype (or close to it...) and i hate it. I have disabled it, used antTek file explorer to delete swype.apk in root/sys/app and also the swypecore in root/sys/lib and ALSO the swype folder in data/data. swype is still on my phone. I am confused! My superuser has granted anttek permission and blah blah, but the files will not delete no matter what i try to do. i just want to update to the newest beta version of swype since the stock one is horrible. any help would be greatly appreciated.
I would have posted this in Dev section, but too few posts on my account and it has denied me...
here are my specs
Current Device: Samsung Fascinate
Current ROM: PWGB EH09 ROM v2.0b3
Current Radio: EC09
Current Kernel: Stock EH09 Kernel
Thank you to anyone who can help! And a BIG Thank You to the devs who put this rom together. So far it is the best I have ever used (and i've tried them all...i think... lol) anyway thanks again!
EDIT: Before doing any of this, naturally, i kill the running swype process and delete the swype installer...

Dont post this type of thing in Dev. Section...this has nothing to do with development.

i figured as much. maybe q+a would be better?
btw, do you have any advice for my swype issue?

I used Titanium Backup to remove swype 2. Worked ok for me. Was able to install swype 3 beta after that

Are you giving the program R/W ability within the folder?
Make sure you pick something like Android Keyboard before you try and uninstall.

FDro said:
Are you giving the program R/W ability within the folder?
Make sure you pick something like Android Keyboard before you try and uninstall.
Click to expand...
Click to collapse
thank you sir! I actually deleted the anttek file explorer...cuz its no good... paid for root expl. and did just what you said and now i have the excellent swype beta working on my phone! thank you again!

if you think removing swype was a pain...
I replaced the bootanimation.zip in /system/media...and change the name of original bootanimation.zip & still it played original and the new zip had no affect on boot up at all.
I placed a new bootanimation.zip in /data/local and still same result.
I changed the permissions using Terminal Emulator and also tried the same with a file manager to no avail.
I even deleted the original bootanimation zip and also the one I was trying to install and the phone still booted up as if nothing was ever changed. I eventually bumped something on the screen while changing hands when file snooping and maybe deleted something so I reflashed the PWGB rom again and started over.
I have issues with the USB settings magically being set to "Samsung KIES" [almost]everytime I plug it into my PC, even though I set to MASS Storage or ALWAYS ASK before hand.
any fix on that would be appreciated..
OH BY THE WAY, I LOVE THIS PWGB ROM, I REALLY DO!!!!
***********as of 10/21/11 I give up on trying to change the bootanimation... I have spent too long on that project for nothing.