Remove autoupdate Market - Wildfire General

How i can remove autoupdate of market?
I open market and have new version. Then i go on application, uninstall update and have old Market. After some time i have new market again.
New market on my wildfire is very slow and FC, and if i have luck to find something, get error to insufficient disl space or app is not compatible.....
With old Market don't have problems. And i want remove autoupdate of Market..
Please someone...

The answer to your question was in the next thread to this one!
Freeze the updater with titanium backup.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
The answer to your question was in the next thread to this one!
Freeze the updater with titanium backup.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
what if I don't have donate version?

dengseng said:
what if I don't have donate version?
Click to expand...
Click to collapse
Simply put.......... get it, or find a different app with root access to freeze it.
We suggest titanium because its the best at what it does, and is worth every penny to a serial flasher.
That sounds a bit wrong!
Sent from my HTC Wildfire using xda premium

Titanium don't help me
Titanium don't help me, but:
Root users:
1. Root explorer - goto system/apps (press mount r/w - if don't press that you will get message for read only)
2. delete "market updater" and com.vending... (something like that - file have vending in name)
3. reboot
4. download old market from here, and install
5. reboot
6. check again in system/apps if exists market update (if no exists, than is OK)
7. with titanium backup make market like system app
7. run market

mozvatic said:
Titanium don't help me, but:
Root users:
1. Root explorer - goto system/apps (press mount r/w - if don't press that you will get message for read only)
2. delete "market updater" and com.vending... (something like that - file have vending in name)
3. reboot
4. download old market from here, and install
5. reboot
6. check again in system/apps if exists market update (if no exists, than is OK)
7. with titanium backup make market like system app
7. run market
Click to expand...
Click to collapse
How to put market back in system using titanium backup???

Don't just bluntly delete the apk, disable it! From a root shell, enter
pm disable com.android.vending.updater
There, it's "frozen". No need for a paid app, S-Off or whatever. Just root.

Yeh but not everyone is as fluent as you in adb, damn took me 4 days just to get it setup correctly and now a month later I'm still learning the basics. With TB its a simple long press on the app and freeze but if you don't have adb its a long process installing for first time and then learning the commands.
Sent from my HTC Wildfire using xda premium

4 days to download the SDK and run it? Did you order a new PC in the process?
EDIT: Consider installing ConnectBot or Android Terminal Emulator. That way you don't need adb and the soft keyboard is good enough for the occasional tweak.

Like i said smartass not everyone is as up to date as you may be, bear in mind that i only bought my first android phone 6 months ago, only found xda 4 months ago and have never really tried to hack anything before except a few games.
It wasn't the downloading that was the problem with adb it was the instructions i was following, they were a little misleading as to where everything should be so as i was getting errors left right and centre so i decided to look further into it and realised i was missing things and a few things weren't in the right place, i never asked for help though mate figured it all out on my own and it's perfect now.
All i'm trying to say is the people having these problems most probably haven't got a clue how to use adb or the terminal for that matter as if they did they probably wouldn't be here asking questions therefore giving them the easiest, quickest possible way to solve there problem is best imo.

You're probably completely right about that, sorry for being a "smartass".

henkdv said:
Don't just bluntly delete the apk, disable it! From a root shell, enter
pm disable com.android.vending.updater
There, it's "frozen". No need for a paid app, S-Off or whatever. Just root.
Click to expand...
Click to collapse
I tried that but I couldn't update any app from the market when disabled.
EDIT: it is not because of that but after removing market udpates it behaves strange, seems that I am able to install 1 or 2 updates but any successive update fails. I will try to get the log to see what is the problem.
EDIT2: seem to be caused by low memory

That's odd, mine still auto-updates applications (but not the market itself).

antish said:
How to put market back in system using titanium backup???
Click to expand...
Click to collapse
Yes, please explain me someone!
Thanks!

Scratch0805 said:
Like i said smartass not everyone is as up to date as you may be, bear in mind that i only bought my first android phone 6 months ago, only found xda 4 months ago and have never really tried to hack anything before except a few games.
It wasn't the downloading that was the problem with adb it was the instructions i was following, they were a little misleading as to where everything should be so as i was getting errors left right and centre so i decided to look further into it and realised i was missing things and a few things weren't in the right place, i never asked for help though mate figured it all out on my own and it's perfect now.
All i'm trying to say is the people having these problems most probably haven't got a clue how to use adb or the terminal for that matter as if they did they probably wouldn't be here asking questions therefore giving them the easiest, quickest possible way to solve there problem is best imo.
Click to expand...
Click to collapse
Totally agree. I to this day still have no idea how to use adb or fastboot!!! When I have tried I have failed miserabley lol.
On topic, I personally just deleted market updater from the rom zip before I flash the rom and have no problems with AP updates.
Lol I must be a smarter arse to get away without using sdk, adb or fastboot for so long.
sent from my wilderbeast:buzz

you do not need to use adb. Just open the terminal emulator and type
Code:
$ su
confirm granding superuser priviledges
prompt should be changed from $ to #
Code:
# pm disable com.android.vending.updater
thats all.
you can restore it similarily using the "pm enable com.android.vending.updater" command.

cceerrtt said:
you do not need to use adb. Just open the terminal emulator and type
Code:
$ su
confirm granding superuser priviledges
prompt should be changed from $ to #
Code:
# pm disable com.android.vending.updater
thats all.
you can restore it similarily using the "pm enable com.android.vending.updater" command.
Click to expand...
Click to collapse
worked for me thanks a lot bud

cedriccc said:
worked for me thanks a lot bud
Click to expand...
Click to collapse
I just repeated what henkdv wrote before. ;-)

And I got the idea from The_Complete_Noob
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

[Guide] Get Swype working without having to edit settings.db

After reading the Swype thread multiple times, it seemed like I was going to have to sack-up and edit settings.db, potentially bricking my Kindle Fire. Well, ignorance, and thick-headedness and a little luck combined to allow me to get it working with what turned out to be a very simple work around.
First, you will of course need to be rooted. I used the method outlined on www.rootkindlefire.com, but others have used Super 1 click, or Zergrush. Whatever floats your particular boat.
Second you'll need the Swype.apk, and a root explorer type app.
Once you've got all that, go ahead and install Swype normally, then navigate to data/app and move the Swype.apk to system/app. Go to a text field and long press to get the input method popup and select Swype, or use Nook Tools app (Swype should start force closing), select kindle keyboard again if you like and reboot, or just reboot (without reselecting Kindle keyboard rebooting takes a while but will happen, just wait). Once you've rebooted, install Swype again. It will tell you it's a system app but your data will be saved blah blah. Once that's done, you should be good to use Swype without issue.
If you want, you can then go ahead and unroot and it should be good. Actually, the only reason you need root is for when you move the apk to system/app. After that, all should work with or without root.
If you get more force closes, just reinstall Swype again. This worked for me on two different kindles so far, so I'm confident, as long as you follow the instructions, it will work for you too.
Sent from my Digital Brick
Edit: fixed Swypeisms
nope didnt work!!!!! bummer
I have made many changes to my kindle and getting swype to work is not one of them. I can never get it show up with either nook tools or long press.
Hmmmm...
Just did it to see how hard it might be. I've been using the thumb keyboard for some time now.
Starting out, I am already rooted...
1) Copied over the Swype Installer (I am a registered user)
2) Logged in.
3) Selected Beta Americas
4) Installed keyboard
5) Used root explorer and navigated to /data/apps
6) Moved the swype keyboard apk file to /system/apps
7) checked permissions to make sure it was rw-r--r-- (it was already)
8) Rebooted device
9) After the reboot, went to a program so that I could long press in the text entry area (I used Touchdown, but anything would have worked)
10) Selected Input Method
11) Selected Swype
Tried to use it, Forced Closed.
12) Went back with Root Explorer and found the /system/app swype apk
13) Clicked on it, wanted to install... let it do it.
14) Tried using the keyboard again.
See below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The one issue I have is that the ability to minimize is not easy to get to... but if you press and hold the swype key, it will go to Preferences and you can just click the back arrow and you have done the same thing. I'm sure there is some other way to do it, but I've not played with it much. Found you can do this by swiping from the Swype key to the backspace key...
Note that I don't normally use Swype, but it seems to work okay for me on my KF.
krelvinaz said:
The one issue I have is that the ability to minimize is not easy to get to... but if you press and hold the swype key, it will go to Preferences and you can just click the back arrow and you have done the same thing. I'm sure there is some other way to do it, but I've not played with it much.
Note that I don't normally use Swype, but it seems to work okay for me on my KF.
Click to expand...
Click to collapse
Swype from the Swype key to the delete key and Swype will minimize allowing you to access your bottom menu bar.
Sent from my Digital Brick
movieaddict said:
nope didnt work!!!!! bummer
Click to expand...
Click to collapse
Strange, worked both times I did it on two different Fires.
Sent from my Digital Brick
Worked out fine for me.
Ok ok for some reason after many previous attempts I got it to work easy peasy.
i can't believe i struggled with this earlier. thanks for everyone's input on this thread. i am a swype user and was missing it.
Worked for me, exactly according to krelvinaz's instructions.
krelvinaz said:
Hmmmm...
Just did it to see how hard it might be. I've been using the thumb keyboard for some time now.
Starting out, I am already rooted...
1) Copied over the Swype Installer (I am a registered user)
2) Logged in.
3) Selected Beta Americas
4) Installed keyboard
5) Used root explorer and navigated to /data/apps
6) Moved the swype keyboard apk file to /system/apps
7) checked permissions to make sure it was rw-r--r-- (it was already)
8) Rebooted device
9) After the reboot, went to a program so that I could long press in the text entry area (I used Touchdown, but anything would have worked)
10) Selected Input Method
11) Selected Swype
Tried to use it, Forced Closed.
12) Went back with Root Explorer and found the /system/app swype apk
13) Clicked on it, wanted to install... let it do it.
14) Tried using the keyboard again.
Note that I don't normally use Swype, but it seems to work okay for me on my KF.
Click to expand...
Click to collapse
Ty so much!!! step , 12, 13, 14 solved my problem!! went back and installed it again and it worked, ty again! to get rid of keyboard just press swype key then home......
Great instructions! I've now got Swype working on my Kindle.
This worked perfectly! Thank you.
Sent from my Kindle Fire
krelvinaz said:
Found you can do this by swiping from the Swype key to the backspace key...
Click to expand...
Click to collapse
I don't know why folks don't take the 30 seconds or the whole minute to read the well done web page of tricks and tips that Swype points you at when you install it. I pointed folks there on the original install Swype thread when they asked about hiding the keyboard. It's right there along with tips on changing case and adding and removing words from the dictionary and all sorts of other goodies. You can still get there with a long press of the Swype key and choosing the learn how to Swype and then more from there.
Sent from my HTC Flyer P512 using Tapatalk
I love swype, but I just can't get this to work! I think it's the Apk I'm using. Could someone please link the one they used. Everytime I try and install the ones from 4shared it says "not installed." It's getting frustrating.
Awesome, I could actually hold conversations on trillian now although the keyboard looks chunky on the fire.
RawRmon said:
I love swype, but I just can't get this to work! I think it's the Apk I'm using. Could someone please link the one they used. Everytime I try and install the ones from 4shared it says "not installed." It's getting frustrating.
Click to expand...
Click to collapse
I have a Tmobile sgs2 and all I did was extract my Swype apk from my phone and the installer too, why get it from a Warez site when u have it on ur phone
Sent from my Kindle Fire using xda premium
movieaddict said:
I have a Tmobile sgs2 and all I did was extract my Swype apk from my phone and the installer too, why get it from a Warez site when u have it on ur phone
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I got it from the swype website. It will download an installer that downloads the swype apk for you.
http://beta.swype.com/
Great! looking forward to playing with this.
Excellent!!! using now Swype
Glad this is helping, I really didn't like the idea of editing my settings data base, but I really wanted Swype, and so did my wife, so when I figured it out I thought it would be good to share.
Sent from my Digital Brick

[request] effective method to prevent OTA updates

Since every method proposed in the thread over in the General forum to prevent updates doesn't work, even having custom TWRP recovery, i'm reaching out to the developers to ask for help on this. I suspect ADCP is involved myself but have no way to trace it.
What if I set /cache to read only? That apparently is where the .bin gets written to by whatever process downloads it, and from there it's read by recovery. Is /cache used by anything else on a typical Android system?
Not everyone wants to use CM7 but that appears to be the ONLY thing that "breaks" OTA updates. I'm sure there's some link in the chain we could interrupt to stop this creeping menace. I'm sure i'm not the only person with 6.2 rooted sitting here with wifi off!
Just a suggestion, but if you set the folder kindleupdates on the sdcard to read-only (it's where updates are downloaded to), would that break OTA updates?
jb0ne said:
Since every method proposed in the thread over in the General forum to prevent updates doesn't work, even having custom TWRP recovery, i'm reaching out to the developers to ask for help on this. I suspect ADCP is involved myself but have no way to trace it.
What if I set /cache to read only? That apparently is where the .bin gets written to by whatever process downloads it, and from there it's read by recovery. Is /cache used by anything else on a typical Android system?
Not everyone wants to use CM7 but that appears to be the ONLY thing that "breaks" OTA updates. I'm sure there's some link in the chain we could interrupt to stop this creeping menace. I'm sure i'm not the only person with 6.2 rooted sitting here with wifi off!
Click to expand...
Click to collapse
Unregistered fires will not get OTA updates. Renaming com.amazon.dcp.apk to com.amazon.dcp.apk.bak will unregister your fire but you will be able to sign into and use all of the amazon services individually.
neilrl79 said:
Unregistered fires will not get OTA updates. Renaming com.amazon.dcp.apk to com.amazon.dcp.apk.bak will unregister your fire but you will be able to sign into and use all of the amazon services individually.
Click to expand...
Click to collapse
Somone just posted that their unregistered Kindle has been updated! There is no escape
Somebody on 6.2 delete /system/etc/otacerts.zip and see if it still updates
Sent from my Galaxy Nexus using XDA App
JackpotClavin said:
Somebody on 6.2 delete /system/etc/otacerts.zip and see if it still updates
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I just went to do that in File Expert, and I don't have a /system/etc/otacerts.zip.
Any other possible locations for that file? I'll try it.
Edit: Found it in /system/etc/security. It has a 1.6kb file called releasekey.x509.pem in it. Renamed to otacerts.bak
Edit2: Just to be safe, moved the file to my sdcard and deleted it from /system/etc/security. Rebooted ok, temp unrooted, Amazon Videos works, my books work, everything seems ok. Note that I am also one of those who disabled OTASilentInstall as well though that doesn't seem to have mattered for some.
bus_ter said:
Somone just posted that their unregistered Kindle has been updated! There is no escape
Click to expand...
Click to collapse
Interesting, I wonder if they recently unregistered it,after the update had already downloaded and was just waiting to install. My fire has never been registered and has never seen an OTA, in fact a couple of amazon techs told me that it was unable to be updated while unregistered. Although now that i think about it, I can't imagine amazon techs know anymore than anyone else
Wrong forum... Rename /system/etc/otacerts.zip does help.
this would be great. at least then we could edit the binarys before updating to include FFF and TWRP.
Mine is still on 6.2 with these methods.
How to disable auto software update OTA on Kindle Fire?
JayceOoi said:
Mine is still on 6.2 with these methods.
How to disable auto software update OTA on Kindle Fire?
Click to expand...
Click to collapse
Yes, Jayce, but there are people reporting use those methods and still getting the update.
I added another layer of protection, the program Droidwall. I allowed Amazon Apps and Amazon Videos plus a bunch of others but did not allow ADCP. Now if I browse to Amazon App Store, buy an app, it no longer pushes to my Kindle, despite the web page saying just go to the Amazon App store App on my kindle and it would download automagically. I had to manually initiate a download of the app. So either otacerts.zip or firewalling off ADCP disabled remote push of apps -- and hopefully disabled remote push of updates, that part remains to be seen.
new method
new method (not confirmed yet i think)
Kindle Fire 6.2.1 breaks root and you cannot re-root. To prevent this, simply install DroidWall. If you are afraid of downloading the update and want to keep wifi disabled, just do a google search for Droidwall.apk and sideload.
Once installed, launch Droidwall. Make sure the mode says "Mode: White list (allow selected). You will have to manually select which apps to give Wifi access to (I selected Email, Browser, Netflix, and Amazon Video on Demand). You should only select the apps you REALLY want to give access to. Then hit Menu and Apply Rules. Enable Wi-fi, and you should be good.
I tested while running Wireshark and watched the bandwidth according to my Tomato router - no more huge files being downloaded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DroidWall : https://market.android.com/details?id=com.googlecode.droidwall.free
or : http://code.google.com/p/droidwall/
source : http://gizmodo.com/5870339/how-to-keep-your-kindle-fire-rooted-and-update+free
Has your log of the app shown you anything?
Where does it log to?
This works if you rename OTASilentInstall.apk to OTASilentInstall.apk.bak and apply the rooted 6.2.1 update. NOTE when you apply the update you have to rename the apk again.
Sent from my still rooted Kindle Fire using xda premium
jb0ne said:
Where does it log to?
Click to expand...
Click to collapse
the app has a log file you can turn on. You view it via the app under more in settings of the app.
http://i.imgur.com/sRDb6.jpg
zirooo said:
new method (not confirmed yet i think)
Kindle Fire 6.2.1 breaks root and you cannot re-root. To prevent this, simply install DroidWall. If you are afraid of downloading the update and want to keep wifi disabled, just do a google search for Droidwall.apk and sideload.
Once installed, launch Droidwall. Make sure the mode says "Mode: White list (allow selected). You will have to manually select which apps to give Wifi access to (I selected Email, Browser, Netflix, and Amazon Video on Demand). You should only select the apps you REALLY want to give access to. Then hit Menu and Apply Rules. Enable Wi-fi, and you should be good.
I tested while running Wireshark and watched the bandwidth according to my Tomato router - no more huge files being downloaded.
DroidWall : https://market.android.com/details?id=com.googlecode.droidwall.free
or : http://code.google.com/p/droidwall/
source : http://gizmodo.com/5870339/how-to-keep-your-kindle-fire-rooted-and-update+free
Click to expand...
Click to collapse
Hi, but just wanted to confirm will this work or will it still update??
Has anyone tried this?
icebuck said:
Hi, but just wanted to confirm will this work or will it still update??
Has anyone tried this?
Click to expand...
Click to collapse
I was using the Droidwall method all day yesterday and today only allowing Netflix, Youtube, Pandora, Spotify, Onlive, Dolphin HD and Market Place wifi access and Just a few minutes ago my kindle was attempting to download and install the update while I was pushing a few apps and I did adb reboot and before it could finish and I'm still at 6.2 but now I've just disabled all wifi access which sucks.
dev/null/ said:
I was using the Droidwall method all day yesterday and today only allowing Netflix, Youtube, Pandora, Spotify, Onlive, Dolphin HD and Market Place wifi access and Just a few minutes ago my kindle was attempting to download and install the update while I was pushing a few apps and I did adb reboot and before it could finish and I'm still at 6.2 but now I've just disabled all wifi access which sucks.
Click to expand...
Click to collapse
Same err...My WiFi is off.
Until some solid solution is found to stop these forced updates.

SuperUser update available now! 06/30/12

* New update released today. Fixes settings and update binaries issues users were experiencing.
Binaries updated to 3.1. OTA survival option added, and temporary unroot selection.
MB860, CM7.2.0, Faux 026b1 1Ghz
On my atrix binaries were update but give me error! on obtaining root access in binary updater, but i still can use root apps
salgato said:
On my atrix binaries were update but give me error! on obtaining root access in binary updater, but i still can use root apps
Click to expand...
Click to collapse
If you really want the 3.1 superuser, grab Zeppelinrox's supercharger startup kit.zip. He has it included as a script that will successfully install it. But, I too am sticking with 3.07 on CM7 ROMs.
~Sent from my Unlocked, Rooted, Faux 1.45gHz Motorola Atrix 4G~
I updated to the new version. The binary updated for me, but it took 3 tries. However, it seems the settings menu is broken. Whenever you click it (it is now a wrench in the top right corner) it causes the app to FC. It seems a lot of people are having this issue based on the reviews that are being posted.
FC for me too.
Dark9781 said:
I updated to the new version. The binary updated for me, but it took 3 tries. However, it seems the settings menu is broken. Whenever you click it (it is now a wrench in the top right corner) it causes the app to FC. It seems a lot of people are having this issue based on the reviews that are being posted.
Click to expand...
Click to collapse
+1 it did update my binarys but it does fc on the settings and i can still use rooted apps
Sent from my MB860 using Tapatalk 2
I saw the available update too. I remember back on my flipside that I got an update and it broke also so I was cautious about updating this. Seems like every update for su breaks at first then they get the kinks out and in some time will re-release a working version. Thanks for the heads up.
Edit: is this for all su users? Hubby has a rooted epic touch. Should I not update it on samsung as well?
Switched to SuperSU a few weeks ago, I'll never look back.
pre4speed said:
I saw the available update too. I remember back on my flipside that I got an update and it broke also so I was cautious about updating this. Seems like every update for su breaks at first then they get the kinks out and in some time will re-release a working version. Thanks for the heads up.
Edit: is this for all su users? Hubby has a rooted epic touch. Should I not update it on samsung as well?
Click to expand...
Click to collapse
Seems to be a multiple platform problem from what I read on the Playstore reviews.
Edit: settings menu is still broke, but i managed to get the latest binaries on CM7.2.0
Edit2: New update released today. Fixes settings and update binaries issues.
MB860, CM7.2.0, Faux 026b1 1Ghz
I'm still having issues on 7.2 Final. The FC issue from last seems to be fixed but I still cannot update the binaries.
It's stuck on "Making sure new su works..."
I've cleared all the caches, uninstalled all previous updates, etc...
UPDATE: Like someone else mentioned, it me took 3 attempts to successfully update. Each try required giving SU access.
Ever since I updated superuser the first time, my phone has been acting up. Now I cannot provide su rights to titanium backup.
Edit: I am now RSD flashing ATT 141 SBF. I will unlock bootloader, then reflash everything. I hope I can have my root rights back. Crossing my fingers!
MB860, CM7.2.0, Faux 026b1 1Ghz
Soldier-2Point0 said:
Ever since I updated superuser the first time, my phone has been acting up. Now I cannot provide su rights to titanium backup.
MB860, CM7.2.0, Faux 026b1 1Ghz
Click to expand...
Click to collapse
Yesterday when we were running into issues with the update I managed to revert back to the old version. Here is what I did.
1. Uninstall Superuser
2. Go to the official Superuser website with the archived files:
Direct Link: http://hosted.androidsu.com/superuser/
3. Download Superuser-3.0.7-efghi-signed.zip.
4. Open it to the system/app directory
5. Pull the Superuser.apk file out of the directory
6. Move it to your phone and install
Alternatively, you can download a zip app (winzip for example) from the android market and install it directly from the zip.
I do recommend once you get the older version reinstalled go to su binary and make sure you are on the version before 3.1. 3.1 doesn't play nice with the old app.
After doing all this last night I was able to update Superuser this morning without any issues.
Dark9781 said:
Yesterday when we were running into issues with the update I managed to revert back to the old version. Here is what I did.
1. Uninstall Superuser
2. Go to the official Superuser website with the archived files:
Direct Link: http://hosted.androidsu.com/superuser/
3. Download Superuser-3.0.7-efghi-signed.zip.
4. Open it to the system/app directory
5. Pull the Superuser.apk file out of the directory
6. Move it to your phone and install
Alternatively, you can download a zip app (winzip for example) from the android market and install it directly from the zip.
I do recommend once you get the older version reinstalled go to su binary and make sure you are on the version before 3.1. 3.1 doesn't play nice with the old app.
After doing all this last night I was able to update Superuser this morning without any issues.
Click to expand...
Click to collapse
Everything is working well after flashing 141 sbf, unlocking then re flashing. I hope this problem does not come back.
Edit : Auto allow permission approval is broken.
MB860, CM7.2.0, Faux 026b1 1Ghz
Question, and I've tried searching but it's hot here and my head is starting to hurt haha
When "-rwsr -xr -x" is in RED under the 'su binary' field, does that mean I need to fix the permissions in recovery? Thanks for the help!
WangChung81 said:
Question, and I've tried searching but it's hot here and my head is starting to hurt haha
When "-rwsr -xr -x" is in RED under the 'su binary' field, does that mean I need to fix the permissions in recovery? Thanks for the help!
Click to expand...
Click to collapse
Use root browser to navigate to /system /xbin. Then scroll down to find "su". Long press the file and select "permissions". Manually change the permissions on the "su" file as seen on screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MB860, CM7.2.0, Faux 026b1 1Ghz
Soldier-2Point0 said:
Use root browser to navigate to /system /xbin. Then scroll down to find "su". Long press the file and select "permissions". Manually change the permissions on the "su" file as seen on screenshot.
MB860, CM7.2.0, Faux 026b1 1Ghz
Click to expand...
Click to collapse
Did that, made MORE stuff go into red text. I know the latest version of SU has messed some stuff up. Tried to fix permissions in recovery, didn't fix anything either.
Just updated right now. Everything seems fine and working correctly.
So this is fixed? I've been avoiding that update
Sent from my MB860 using xda app-developers app
aaron.a said:
So this is fixed? I've been avoiding that update
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Yes, the latest version runs as it should.
WangChung81 said:
Did that, made MORE stuff go into red text. I know the latest version of SU has messed some stuff up. Tried to fix permissions in recovery, didn't fix anything either.
Click to expand...
Click to collapse
Those are my default permissions for the "su" file. I have not made any change to that file. Check and see if your ADB DEBUGGING is turned off.
MB860, CM7.2.0, Faux 026b1 1Ghz

Root method likely possible via modified Binary method...

sa·yo·na·ra
ˌsīəˈnärə/
GSLEON3 said:
ABSOLUTELY DO NOT, DO NOT TRY THIS IS WILL LIKELY BRICK YOUR DEVICE!!!
Ok, so I have been able to confirm that using a modified Sony Xperia script, the Binary Root Mothod is able to initiate a desktop restore. HOWEVER, I am woefully unfamiliar with Kindle devices & I have not had time to study the partition structure, so I went no further than initiating the Desktop Full Data Restore mode on the HDX 8.9.
Based on what I have seen thus far, I do believe that root will be possible using existing Binary methods once a HDX desktop backup can be properly modified for these devices. The standard Kindle restore leaves the accept or cancel buttons grayed out. However, as you can see in the attached picture, using a modified version based on a Sony script, allows for the restore selection to be made.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once I have some time, I will see what I can learn about the method Binary uses & see what files are currently included in previous Binary method backup files. In all likelihood, the root process will remain the same for the Kindle line as previous versions. At this time however, unless you know what you are doing, leave well enough alone & lets see what @Hashcode thinks.
Click to expand...
Click to collapse
Just wanted to say thanks for helping the cause.
GSLEON3 said:
ABSOLUTELY DO NOT, DO NOT TRY THIS IS WILL LIKELY BRICK YOUR DEVICE!!!
Ok, so I have been able to confirm that using a modified Sony Xperia script, the Binary Root Mothod is able to initiate a desktop restore. HOWEVER, I am woefully unfamiliar with Kindle devices & I have not had time to study the partition structure, so I went no further than initiating the Desktop Full Data Restore mode on the HDX 8.9.
Based on what I have seen thus far, I do believe that root will be possible using existing Binary methods once a HDX desktop backup can be properly modified for these devices. The standard Kindle restore leaves the accept or cancel buttons grayed out. However, as you can see in the attached picture, using a modified version based on a Sony script, allows for the restore selection to be made.
Once I have some time, I will see what I can learn about the method Binary uses & see what files are currently included in previous Binary method backup files. In all likelihood, the root process will remain the same for the Kindle line as previous versions. At this time however, unless you know what you are doing, leave well enough alone & lets see what @Hashcode thinks.
Click to expand...
Click to collapse
Well at least things are moving here. It's been so sad seeing no development on this thread. I have the KF HDX 7" and willing to offer mine for testing. I've been itching to see at a least root. I also did run the Bin4ry method and the restore reboots but doesn't do anything else.
Really? Unless that's new with the hdx, any backup/restore should work fine. Even if its files are corrupt.
Sent from my KFTT using xda app-developers app
Are you SURE? You know EXACTLY what is pushed in the desktop restore?
I am not familiar with KF Binary or First Aide backup/restore methods, but unless Binary is solely adding the necessary files for root, that could be disastrous. I find it hard to believe that is the case, considering how badly display & performance are affected during the previous HD versions desktop restore methods.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
Are you SURE? You know EXACTLY what is pushed in the desktop restore?
I am not familiar with KF Binary or First Aide backup/restore methods, but unless Binary is solely adding the necessary files for root, that could be disastrous. I find it hard to believe that is the case, considering how badly display & performance are affected during the previous HD versions desktop restore methods.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have manually corrupted files and was able to send them to the device just fine. The restore option was not grayed out, but when you hit that button, it does nothing and just does not restore the data.
Sent from my KFTT using xda app-developers app
r3pwn said:
I have manually corrupted files and was able to send them to the device just fine. The restore option was not grayed out, but when you hit that button, it does nothing and just does not restore the data.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Be careful. I can tell you that I was at one point able to get the SU binary into a temp folder & copied into xbin, however, when I tried to get bb over as well, the device rebooted & I have not been able to get any ADB connection since. I have reset & removed devices, used different pc's & even factory reset the HDX. After four hours I cannot get any ADB access period.
You try using a terminal on the kindle and manually restarting the adbd service? I'm not aware of if you need root access to do so but maybe you can get some debugging output or just get it working in general by tinkering with this. For reference try something like
Code:
stop adbd
start adbd
Edit: also at this point you technically are rooted, I'm not sure if u have to have an apk to interface with the su binary, but after trying to help my friend root his Alcatel phone (don't get me started), the thing is rooted but while trying to get it switched from using supersu to superuser I believed superuser isn't functioning but we still have root access, and I don't believed superuser is in the/system/app directory, so point being, if u can sideload superuser and es file explorer you might be able to fix the situation if busy box caused the problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
good to hear this, hope the rooting method coming out soon!
stunts513 said:
You try using a terminal on the kindle and manually restarting the adbd service? I'm not aware of if you need root access to do so but maybe you can get some debugging output or just get it working in general by tinkering with this. For reference try something like
Code:
stop adbd
start adbd
Edit: also at this point you technically are rooted, I'm not sure if u have to have an apk to interface with the su binary, but after trying to help my friend root his Alcatel phone (don't get me started), the thing is rooted but while trying to get it switched from using supersu to superuser I believed superuser isn't functioning but we still have root access, and I don't believed superuser is in the/system/app directory, so point being, if u can sideload superuser and es file explorer you might be able to fix the situation if busy box caused the problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah, I've tried just about everything I've ever seen or done to resolve abd issues since 2007. Still a no go. Going to give usb otg a try. Otherwise it's RMA & start over. While the SU binary is in place, I still cannot access it. Calls to SU or trying to open the SU app cause an instantaneous FC & reboot.
I'll tell you though, I really like the tablet. Awesome display & the SD800 w/Adreno 330 flat out rocks. This is totally what the Nexus 10 should have been.
I've also been able to determine that Motorola is the OEM. There are Motorola backup files native to the device at least. I am also going to run this weekend & pick up a 1k transistor, to make a Motorola factory fastboot cable, since I gave mine away with an Xperia tablet. With the factory cable, I should be able to issue fastboot commands. That may enable me to devise a BL unlock.
GSLEON3 said:
Be careful. I can tell you that I was at one point able to get the SU binary into a temp folder & copied into xbin, however, when I tried to get bb over as well, the device rebooted & I have not been able to get any ADB connection since. I have reset & removed devices, used different pc's & even factory reset the HDX. After four hours I cannot get any ADB access period.
Click to expand...
Click to collapse
How are you sure that you got it into xbin?
Sent from my iPod touch using Tapatalk

Bloatware removing???

Hey guys, I'm currently having a G6 and it's grand. I'm just curious if I can uninstall all the bloatwares to make it even butterier. The only thing I've found that might actually work is this
https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Well I wouldn't have started the thread if that debloater had worked. I already turned on USB debugging and of course did all the required setup. It just didn't work. It's just....blank.
So I'm wondering if anyone has successfully attempted this method.
Thanks in advance
You rooted?
pham_dang said:
Hey guys, I'm currently having a G6 and it's grand. I'm just curious if I can uninstall all the bloatwares to make it even butterier. The only thing I've found that might actually work is this
https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Well I wouldn't have started the thread if that debloater had worked. I already turned on USB debugging and of course did all the required setup. It just didn't work. It's just....blank.
So I'm wondering if anyone has successfully attempted this method.
Thanks in advance
Click to expand...
Click to collapse
With root you can uninstall whatever you don't want.
Without root use adb commands to uninstall apps from the 0 user.
I'm not rooted but I have debloated with this method.
I haven't rooted yet
It's strange, I did everything and the debloater didn't work, it was blank (device connected was red)
christopherrrg said:
With root you can uninstall whatever you don't want.
Without root use adb commands to uninstall apps from the 0 user.
I'm not rooted but I have debloated with this method.
Click to expand...
Click to collapse
Is there a way to install apps from the 0 user as well you can uninstall it using adb commands??
Enviado desde mi X98 Plus mediante Tapatalk
cpasoft said:
Is there a way to install apps from the 0 user as well you can uninstall it using adb commands??
Enviado desde mi X98 Plus mediante Tapatalk
Click to expand...
Click to collapse
I would imagine it should work but sound tedious. I would just install apks from a file manager.
When you remove them unrooted with adb I believe you are only deleting the user profile of the app. I believe it remains fully on the device but instead of being stuck on 'disabled' it removes from the list and uninstalls it just from userland.
Keep in mind without root we only have read access to the system, not write permissions.
christopherrrg said:
I would imagine it should work but sound tedious. I would just install apks from a file manager.
When you remove them unrooted with adb I believe you are only deleting the user profile of the app. I believe it remains fully on the device but instead of being stuck on 'disabled' it removes from the list and uninstalls it just from userland.
Keep in mind without root we only have read access to the system, not write permissions.
Click to expand...
Click to collapse
So it won't work... I would like to install some applications as system applications, but I guess this is impossible without rooting, and the H870DS is not going to be rooted soon...
Enviado desde mi X98 Plus mediante Tapatalk
cpasoft said:
So it won't work... I would like to install some applications as system applications, but I guess this is impossible without rooting, and the H870DS is not going to be rooted soon...
Enviado desde mi X98 Plus mediante Tapatalk
Click to expand...
Click to collapse
As would I friend, H873 over here. I'd like to build some custom roms but who knows if we will ever get an unlock.
pham_dang said:
Hey guys, I'm currently having a G6 and it's grand. I'm just curious if I can uninstall all the bloatwares to make it even butterier. The only thing I've found that might actually work is this
https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Well I wouldn't have started the thread if that debloater had worked. I already turned on USB debugging and of course did all the required setup. It just didn't work. It's just....blank.
So I'm wondering if anyone has successfully attempted this method.
Thanks in advance
Click to expand...
Click to collapse
I used the adb method ... works like a glove ...
adb debloating method on reddit
when I try using adb method (from the reddit link)I get an error 'pm' is not recognized as an internal or external command... any ideas? thanks
EDIT: solved, need to run adb shell command first, worked!! all apps (even system ones)I uninstalled with this method are gone
Jostian said:
when I try using adb method (from the reddit link)I get an error 'pm' is not recognized as an internal or external command... any ideas? thanks
EDIT: solved, need to run adb shell command first, worked!! all apps (even system ones)I uninstalled with this method are gone
Click to expand...
Click to collapse
can you please have a more detailed instruction, I'm pretty noob with this adb thing
Firstly you need to install adb on your pc, have you done that? If not then just search for adb xda download. Then install and then open file Explorer and find adb folder and open it. Then anywhere in the Open space of that folder right click your mouse and select open command prompt. Then connect your phone (make sure you have lg drivers are installed) your phone screen may ask for security permission for the pc. In the command prompt window type in adb devices and it should give you device id, then type adb shell, then on next line you can paste the 'pm user....' line up to 0' from the reddit link, then after the 0 leave a space and from the pastebin link copy and page the name of the app you want to delete 'com.lg...' then press enter and the uninstal is done. Do that for each app you want deleted.
Sent from my LG-H870 using Tapatalk
Jostian said:
Firstly you need to install adb on your pc, have you done that? If not then just search for adb xda download. Then install and then open file Explorer and find adb folder and open it. Then anywhere in the Open space of that folder right click your mouse and select open command prompt. Then connect your phone (make sure you have lg drivers are installed) your phone screen may ask for security permission for the pc. In the command prompt window type in adb devices and it should give you device id, then type adb shell, then on next line you can paste the 'pm user....' line up to 0' from the reddit link, then after the 0 leave a space and from the pastebin link copy and page the name of the app you want to delete 'com.lg...' then press enter and the uninstal is done. Do that for each app you want deleted.
Click to expand...
Click to collapse
thank you, i wonder if OTA update would function normally after that debloating procedure
Yes ota will work
Sent from my LG-H870 using Tapatalk
Jostian said:
Yes ota will work
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
It doesn't seem like it has worked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
seems like you had some success's, the failure one's are normally due to those apps not being part of the system, I also had a few failures. and then later on where you have the package manager errors, I'm not sure, maybe just run the process again for those with the error and see.
pham_dang said:
uninstall all the bloatwares
Click to expand...
Click to collapse
Which bloatware do you talk about? My G6 has few "possibly unwanted apps" which are easily to uninstall or can be deativated. Else, I would not buy a phone with official Google-Android, when I don't want those services.
Something else, whenever "do not disturb" is on, I have a persistent notification. Is it possible to get rid of that?
ASW1 said:
Something else, whenever "do not disturb" is on, I have a persistent notification. Is it possible to get rid of that?
Click to expand...
Click to collapse
Sadly no. It is there to remind you of why it is in fact active.
pham_dang said:
It doesn't seem like it has worked
Click to expand...
Click to collapse
Looks like what happened in the middle there is you pasted text that was meant as descriptive, not literal (the "- AirDrive") which crashed the package manager and then subsequent commands failed until it recovered. Start over at the AirDrive line but be careful not to paste that extra text (the Google Duo and Google Docs lines have it too). You might need to reboot your phone first to restart the package manager.

Categories

Resources