* 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
Related
[TOOL] Unleash The Beast V0.2 (Root, Remove Bloat, Sideloading, Unrestricted & More)
My website: www.peteralfonso.com
Follow me on twitter
{
"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"
}
UNLEASH THE BEAST V0.2
File Size = 2.66 MB
* Will root your Samsung Captivate (if you already have root that is ok too)
* Can enable sideloading (for installing non market apps)
* Install Busybox & symlinks (V1.17.1)
* Install SQLite3
* Install Wireless Tether App (V2.0.5) (turns phone into a router for free)
* Install Market Access App (V1.0.6) (Can uncensor your market)
* Install News & Weather App (a.k.a. Genie Widget)
* Blocks Advertisements in Apps & Browser
* Removes the AT&T Boot Animation (credit to me!)
* Removes Power On Sound
* Removes Power Off Sound
* Removes AT&T Family Map App
* Removes AT&T Music App
* Removes AT&T Maps App
* Removes AT&T Navigator App
* Removes AT&T Radio App
* Removes AT&T Hot Spots App
* Removes Days App
* Removes Daily Briefing App
* Removes Google Maps (download from market to have the latest version)
* Removes Memo App
* Removes Mini Diary App
* Removes Mobile Banking App
* Removes Mobile Video App
* Removes MobiTV App
* Removes My Files App (Astro File Manager is WAY better)
* Removes Where App
* Removes Write And Go App
* Removes Yellow Pages App
For those of you worried you will need any of these apps there are better replacements for them in the Market. Trust me you will not miss any of them once you flash this tool. If you are still worried I will eventually make a restore tool that will add them back if need be.
Installation Instructions:
1. Download unleashthebeastv0.2.zip
2. Rename to update.zip
3. Place on sdcard (the built in card, not the removable)
4. Boot into recovery mode
(shut off phone, then hold power, volume up, & volume down at the same time)
5. Select "Reinstall Packages"
6. Enjoy, you have now Unleashed The Beast!
Side-loading Instructions:
1. Open a terminal (you can download "Android Terminal Emulator" in the market)
2. Type in: su
3. Type in: sideloading
4. Your phone will reboot and sideloading will be enabled!
Changelog:
Version 0.2
-Downgraded Busybox to V1.17.1 (has more commands)
-Properly symlinked all busybox commands
-Created a sideloading script!
-Added SQLite3
-Updated Wireless Tether to pre8
Wow. Brilliant work man. Good job. I'll test it out when I get home.
Sent from my SAMSUNG-SGH-I897 using XDA App
If you have any suggestions feel free...
Does this enable app sideloading?
Sent from my SAMSUNG-SGH-I897 using XDA App
Im having some issues...
I had to restore to the base image .. again after trying out the i9000 ROM, and now when I run your update.zip from here it only roots the phone.
Nothing else is done.
I have tried running this twice in a row. Let me know what I am doing wrong.
pretty cool.
One thing to note is if you are running the lagfix or intend to it will not work with the newest version of busybox. You will have to revert back to 1.17.
Awesome, I'm looking forward to seeing some buglessbeast on our Captivate!!
You might want to see if you can get this update.zip added to ROM Manager
Good job, flashing now to see if it effects anything else on my phone
One comment. Busybox 1.18 removes a lot of commands, and those of us that want to use the ext2 lagfix have to revert to the more capable 1.17.1. I'd recommmend that you include 1.17.1 in this file instead of 1.18, until a better version of busybox is released.
Update:
Just Flashed Via ClockworkMod Recovery, After Reboot the ATT Startup animation, and sound were still there.
It also did not remove My Files or Google maps, leading me to believe it didn't work.
in clockwork it ran through the updatezip and had said it install successfully
Update2:
Ran through it again, and it said it successfully but did not apply any changes to my current ROM
Update:
Ran in normal recovery and it has seemed to work fine.. I wonder if this is a problem with your update.zip or with clockworkmod recovery
x2 on the ext2 fix
I am watching this thread with much anticipation...
Also, since you can remove the AT&T startup screen, does that mean we can put in a custom startup screen? :think:
I have a silly question. Will this update erase any of my settings ,applications (apps not listed in the first post), and internal memory?
Thanks Guys!
Just out of curiosity, what blocks the ads within the browser and apps? Is it just a host file with blacklisted sites? (kind of like adblock). I've already done much of what Unleash The Beast will do except for the ad blocker.
@Bigfan - I would not expect this to erase any of your settings or other applications because it just applies the root and removes bloatware, but like everyone always warns... there is the potential for it messing something up or erasing data.
I'm going to be following this thread with much anticipation. Keep up the good work!
kennethpenn said:
Does this enable app sideloading?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
No not yet. I may be able to create a script to do so. I will look into it.
rajendra82 said:
One comment. Busybox 1.18 removes a lot of commands, and those of us that want to use the ext2 lagfix have to revert to the more capable 1.17.1. I'd recommmend that you include 1.17.1 in this file instead of 1.18, until a better version of busybox is released.
Click to expand...
Click to collapse
I'm on it captain, thanks for the tip
bigfan2232 said:
I have a silly question. Will this update erase any of my settings ,applications (apps not listed in the first post), and internal memory?
Thanks Guys!
Click to expand...
Click to collapse
Nope, no settings will be lost.
joeybear23 said:
Since you can remove the AT&T startup screen, does that mean we can put in a custom startup screen? :think:
Click to expand...
Click to collapse
Only one way to find out, ill give it a go when I get a moment.
LinuxNewb said:
Just out of curiosity, what blocks the ads within the browser and apps? Is it just a host file with blacklisted sites? (kind of like adblock). I've already done much of what Unleash The Beast will do except for the ad blocker.
Click to expand...
Click to collapse
Correct, just replaces a hosts file. You can still run it with no ill effect even if you have done most of it already.
Thanks for this. I really like being able to easily get rid of all the att crap that is on my phone.
It would be real nice to have it enable side loading apps as well. but thats still an easy fix.
Anyone have a download link to busybox v1.17.1? I seem to have lost it
Awesome work. Will try it tonight.
One quick question. Does it allow you to select which of the listed items it removes? If not, would be a good feature to add. The restore tool will be great too, just in case someone needs to return their phone.
It did the job even on the new I897UCJH2 rom. Excellent work! Thanks
this thing seems to have sped up my phone. Love it. Only issue I'm having is the tether app isn't working.
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"
}
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.
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
All Builds In This Thread Are Considered Stable And Final.
I Am Not Responsible For Any Use Of Information Or Files Posted By Myself Or By Any Other User.
New is built from XAC T700XXU1ANL2 Firmware
This was made for us by @jrkruse who doesn't even own the device but still put it together for us:good:
I thank him greatly for that!
Requirements
Rooted SM-T700 With Custom Recovery
Download
STOCK_T700XXU1ANL2 https://www.androidfilehost.com/?fid=95916177934550989
rooted, deodex, Init.d support, zip aligned
Download
T700XXU1ANL2_Debloated https://www.androidfilehost.com/?fid=95916177934551122
Rooted, DeOdex, Init.d support, Zip Aligned
Boot Sound and USB Connect Removed
All Non-Samsung Removed
Xposed, Root Browser and Quick Boot Added
If you would like something back in that was removed please let me know
Download
EMPTYGALAXYROM T700 v2 https://www.androidfilehost.com/?fid=95916177934551888
- T700XXU1ANL2 Extremely DeBloated
- Deodex, Rooted, BusyBox, Init.d support and ZipAligned
-SFinder and Quick Connect Removed From Pulldown
-Boot And USB Connect Sounds Removed
*Apps Left In App Drawer
BusyBox Free
Calculator
Camera
Clock
Gallery
Google
Google Settings
Internet
Music
Nova Settings
Play Store
Quick Boot
Root Explorer
SPlanner
Settings
SuperSU
Voice Search
Xposed Installer
Recommended Instructions
Download Rom To SdCard
Boot Into Recovery
Wipe Dalvik Cache, Cache, System, Data and Internal Storage [optional]
Install Rom and Reboot
Go through Wizards
[EGR Go To Settings And Sign In To WiFi, Add Google Account and Set Time Zone]
Reboot And Wait For SuperSU Update Notification And Update It
Update SU Binary Normal And Reboot
It's All Yours From There!
OLD DOWNLOADS
EMPTYGALAXYROM v1.3 https://www.androidfilehost.com/?fid=95916177934535221
- A backup ran through a rom kitchen and cleaned up. [Assumed US firmware until I hear different]
- T700XXU1ANL2 Extremely DeBloated [libs, files and *apks]
- Deodex, Rooted, BusyBox, Init.d support and ZipAligned
-Aosp Tick
-SFinder and Quick Connect Removed From Pulldown
-Boot And USB Connect Sounds Removed
*Apps Left In App Drawer
Calculator
Calendar
Camera
Clock
Gallery
Google Settings
Internet
Music
^Nova Settings
Play Store
Quick Boot
Root Explorer
Settings
SuperSU
Xposed Installer
^Nova is the default and only launcher
Special Instructions For Google Now Launcher
You Must First Install Google Search Before The Google Now Launcher
*******************************************
STOCK VERSIONS OF T700XXU1ANL2
Recommended Instructions
Download Rom Of Choice
Boot Into Recovery
Wipe Dalvik Cache, Cache, System, Data and Internal Storage
Install Rom and Reboot
Go Through Set Up Wizard
Reboot
Completely_Stock_T700XXU1ANL2 https://www.androidfilehost.com/?fid=95916177934532866
Rooted And Busybox As Is Odexed Untouched Stock.
T700XXU1ANL2_DORBIZ https://www.androidfilehost.com/?fid=95916177934532867
Deodex, Rooted, BusyBox, Init.d support and ZipAligned
All Bloat. All. I will update this if someone else doesn't make an NL2 debloated.
DRBIZ_T700XXU1ANL2 https://www.androidfilehost.com/?fid=95916177934533222
Same as above without knox, boot & usb connection sound.
Added in data/ Xposed, Reboot & Root Browser
SystemUI.apk https://dl.dropboxusercontent.com/u/9398026/SystemUI.apk
with SFinder and Quick Connect Removed From Pulldown
Use a root browser to replace current in system/priv-app
*WARNING*
This can be a little tricky as the system will force close before you can change permissions.
Instructions
download to SDCard
copy and paste SystemUI.apk to System/priv-app [overwriting current]
quickly reboot
change permissions [you should just need to click off "others/write"]
EMPTYGALAXYTHEME flashable in custom recovery https://dl.dropboxusercontent.com/u/9398026/EGT_V0.1.zip
Theme Info
This is only recommended to be used with stock NL2 Roms for Tab S 8.4
Contains - pngs, xmls and SystemUI.apk
It is very far from done but I figured I'd post it because I use it so maybe you'll want to.
I'm stuck on compiling errors and without time to figure it out. If I add a significant amount of themed parts I'll update it.
{
"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"
}
*******************************************
Developers
Feel Free To Use These Builds How You Like
Although I Would Wait For Official Firmware
This Is An OTA Back Up Ran Through Ricky's Kitchen
Special Thanks To
@Ricky Divjakovski
@EMSpilot
@akash_bd
tbd
tbd
_________________________________________
_________________________________________
Empty galaxy rom...
I just wanted to let you know that I have it installed and have been messing with it for about an hour. Everything seems to be running quickly. So far the only thing I have noticed is that it seems to be running a little warm. I will report back with anything else I come across. Good work!!
I've been working on the theme but the ui is new to me. Still finding stuff. Thanks though @ITSAHERO hopefully as it set in it evened out the temp.
Couple questions
Hello there,
I am interested in installing the completely debloated version you did. Is the IR Blaster and the finger print unlocking the device working? Thanks in advance!!
I haven't tried the ir but finger print works. And you're very welcome.
I'll try the ir and report back. I'm in the middle of an install so it'll be a few..
Added
IR: Tested and fully operational
Best rom I've used.
Hi, downloaded the empty ROM on my tab s t700. Personally I'm not a fan of Nova so I tried installing google now launcher but it doesn't work for me? It installs and stuff alright but it just force closes on me. Now, I'm coming to this ROM from ironrom on which I was running google now launcher but I just can't get it to work on here. Am I the only one a facing this problem?
I'll download and try and report back.
Added-
Yes. You're right.
I removed Google search, sometimes I use yahoo so I like it out.
To use Google Now you need to first install Google search and go through initial setup then download and install Google Now.
The OP has been updated and the Empty Galaxy version has been updated to 1.3.
I had hoped to add a theme to it but it's taking more time than I thought to find everything.
If I get to a usable point with it I'll upload.
The rom ive been waiting for.. thanks dev.. what kernel suits best with it? Can you recemmend any?
I've been using the stock kernel so I can't really recommend yet. I'll give what's available a try today.
I'm using sky-high kernel with this rom, I have to say, my tab S 8.4 has never been smoother, almost as quick as my nexus 9.
Is this a US firmware? I have been using it and lost access to wifi channels 12 and 13. The tab could not detect my home network anymore. Europe here... Thx for all the work you've put into this.
Brgds
Sent from my GT-I9505 using xda premium
Everything has been working well for me with the stock kernel. Great ROM. :good:
rlrmineiro said:
Is this a US firmware? I have been using it and lost access to wifi channels 12 and 13. The tab could not detect my home network anymore. Europe here... Thx for all the work you've put into this.
Brgds
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
My apologies, that didn't even cross my mind. This is a backup ran through a rom kitchen and cleaned up. But it was an ota so I've got to assume it's US. If I get a chance I'll look into it.
Best RoM used yet! Keep up the good work.
Thanks.. I'm not sure where I'm at with development on the tab s. Glad the roms are getting used. I'm still waiting for the official nl2 download. My favorite thing about the tab is having a device not connected to a carrier! And it really makes it so we don't need very many apps to start.
reggie cheeks said:
Thanks.. I'm not sure where I'm at with development on the tab s. Glad the roms are getting used. I'm still waiting for the official nl2 download. My favorite thing about the tab is having a device not connected to a carrier! And it really makes it so we don't need very many apps to start.
Click to expand...
Click to collapse
Agreed, it's so relaxing.
Setup time on a fresh install is so short