5.3.6.4? - Fire HD 8 and HD 10 General

This is downloading on my device? Is this going to brick it?

No it's fine. Lots of us received that update the days. I don't see anything new but the performance after the update seems very good.
Sent from my iPhone using Tapatalk

Why would you think it would brick your device?
Did any of the previous updates brick it?
I know the number looks strange - it really should be 5.6.... not 5.3, but that's a mistake on Amazon's end as the "Learn more" link to the User Guide has the correct number.

OP had probably downgraded his tablet to a earlier version of FireOS like I did and installed the play store and nova launcher. I havent used it in a few days but when i got it out today, it said it downloaded and installed 5.3.6.4 on 11/11/18 at 1:16am... which is weird because I had previously used this guide to downgrade to 5.4.0.0 ( https://forum.xda-developers.com/amazon-fire/help/fire-7-2017-7th-gen-downgrade-debloat-t3699937 ) and this "update" seems to have downgraded it even further. But nothing has changed except the version number. Lockscreen ads and all the bloat is still gone and nova is still my launcher, so having the update message appear is very head scratching...
BTW, i did the downgrade to 5.4.0.0 MONTHS ago, and have never seen an update message until today. In fact, if I went into the Device Options and selected System Update, it wouldn't allow me into the setting...it would just kick me back to the home screen. Now it DOES allow me into the setting. Very strange.

5.3.6.4 Update remove root?....
After receiving the 5.3.6.4 update on my HD 10 (11/15/18) -
Lock Screen Ads re-appeared on reboot
Titanium Backup - "no longer finds root" (and in turn, no longer works)
SuperSu - No longer works
Nova Launcher remains in-place oddly enough
I have since theoritically (read on) uninstalled all apps mentioned above and re-rooted via kingoroot and can access a root prompt via ADB (id reflects uid=0(root) gid=0(root) context=u:r:init:s0), however I have been unable to update the binaries for SuperSU despite multiple re-installs and reboots (I'm running the previously working v2.79 btw). Additionally, when I now run a fresh install of Titanium BackUp, all I get is an ongoing "Detecting SU & Busybox..." message onscreeen that leads to no where (I just re-installed BusyBox prior) AND when I run Root Checker, it relects no root as well, despite both kingoroot reflecting root within it's app and my ability to run su via an adb shell on my PC., though please also note that I am unable to run su via a shell/terminal emulater installed on the device ("su: not found").
Thoughts?....thanks in advance for the assist.
Peace.

Related

Busybox issues gingerbread Samsung galaxy tab

Hello,
Id like to request some support.
I have successfully rooted my galaxy tab (7 inch model, gingerbread) and that seems to be working correctly: I have that super user app install, and every time I launch a root like app (such as shoot me etc..) there's the pop up asking for permission.
Problem comes at the next step: busybox. I have downloaded the busybox installer from the market. Followed the steps... latest message I saw from the app is that everything went smooth, but when I launch apps that require busybox (such as Shark), application says it cant find busybox...
After rebooting, I go again to the busybox installer (I got the two of them now available on the market). Once says I don't have root, which BS, and invites me to go to the super user app and forget the settings about that application. That I do, and doesnt do anything. App request root priveleges, which I grant, but it will still tell me that it doesnt have them.
The second busybox app goes a little further: It gets the root powers (which once again proves my phone is definitely rooted) and it says something like phone is rooted and many copies of busybox were encountered.
Apparently I got more than a single copy. But when I try to "re-install" it, this is what I get: can not install because system is not in read write mode.
And i did remount the system folder with root tools pro but I still get the same message...
So, how could I resolve this situation?

[Q] BusyBox Updater Breaks Root Access

There have been a couple similar posts, but none seem to provide any help, so I apologize for creating a new one if the answer is already out there.
With that said, I recently purchased a new LG Nitro HD and promptly used SuperOneClick to root it. Everything seemed to work fine (on the first try); I rebooted the phone, SU was there, all seemed well. The first thing I tried to use the root access for was to change the LCD Density, and that didn't work - so I tried to update the BusyBox on my phone, using "BusyBox Installer". After I did that, my root access seemed to "break", by which I mean superuser is still installed, and SuperOneClick reports my phone as rooted, but SuperUser cannot authorize apps (or doesn't even try) and attempting to run an app that requires root access simply fails, suggesting that my phone is not rooted. Typically, I would ODIN the SOB and be done with it, but I cannot find any PIT files for the Nitro HD (and I am assuming that would be necessary for me to do anything with ODIN). I've also tried using SuperOneClick to unroot and reroot the device, but now it hangs on step 7 every single time.
Does anyone out there have any suggestions at all?
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Please advise - I am seeing this as well
SolusCado said:
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Click to expand...
Click to collapse
The new MeanROM ICS uses the new SuperUser - however, it breaks root access as you mention. Please advise the corrective action. Send PM if ncessary

SuperUser 3.13 problems

After finally getting my HTC Status (ChaCha), rooted (the first phone I got rooted) with XTC Clip (this is a device to unlock the bootloader and carrier lock on HTC phones), ClockworkMod, and SuperUser. After updating it that night, the apps I had granted root permissions stopped being able to use root functions (like ES Explorer's root read/write function) or not all, except for AdFree, which continued to keep most ads at bay. Now SuperUser no longer shows any apps listed, and attempts to update the binaries but gets stuck at "Gaining root access" and crashes eventually. The Update Fixer program gets stuck at 'Waiting for root access', not unlike Titanium Backup Pro, which is stuck at 'awaiting root access'. I also tried Super Super User as well, and it was stuck on "The SU binary needs to be updated. Continue? Installing, please wait ..." After more than an hour of waiting, I quit. Same for SuperUser Update Fixer. I also uninstalled the SuperUser update and found that didn't fix anything. I reinstalled Titanium Backup Pro too, same results. I have read that some folks have had success installing Busybox (separate from Tiny Busybox that is part of SuperUser), but I don't see how I would install it if I can't get root permissions! After reading the comments posted on Google Play about SuperUser following the update, I can see plenty of people have had various sorts of problems with SuperUser now. Any thoughts on how to remedy this, besides badgering the author of the software? (I did post feedback to Google Play, nothing hostile or anything, trying to be as precise as possible.)

Q. Root method for Hannspree SN14T71

Help. Looking for root method for Hannspree SN14T71 on 4.2.2.
Please any help is appreciated.
Sent from my SCH-I605 using XDA Premium 4 mobile app
I'm in the same boat
tennisjunkie said:
Help. Looking for root method for Hannspree SN14T71 on 4.2.2.
Please any help is appreciated.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi! I bought the Hanspree 13.3 and noted that when I bought it one of the reviews said that it came rooted from the factory. Sure enough, I downloaded Root Checker and it says that I have Root. Unfortunately when I went to install Superuser Pro it installed but then says I need to update the binary (and I've done this multiple times on my Android phones or other tablets, it's a hobby what can I say?) it fails to update. I tried getting the binary direct from Sterickson and installing it through Recovery but that failed too. Busybox won't install because it says SU is screwed-up or I don't have root..
I was just hoping to find some ROM that could take advantage of this large screen, out of the box it boots and looks like a tablet for the sight-impaired (no offense) because all it does is display these huge icons and huge text (even after reducing text size to small). From all that I have seen today it looks like nobody is developing for this device. I guess we should be happy that we got 4.2.2 out of the box, at least we're ahead of most others..
Anyone have any ideas???
Chris R.
Ok. I have had the same experience and I found out the "solution" I believe. Did you try superSU? Because I tried to install superuser and it failed also but supersu did not. Try that and let me know.
Sent from my SCH-I605 using XDA Premium 4 mobile app
same wish here
Mine doesn't seem to be rooted. Any fail safe way to check if it is rooted or not? Want to speed this thing up and get the programs off of the RAM. I end up with only 300-400 mb available.
crodgers79 said:
Hi! I bought the Hanspree 13.3 and noted that when I bought it one of the reviews said that it came rooted from the factory. Sure enough, I downloaded Root Checker and it says that I have Root. Unfortunately when I went to install Superuser Pro it installed but then says I need to update the binary (and I've done this multiple times on my Android phones or other tablets, it's a hobby what can I say?) it fails to update. I tried getting the binary direct from Sterickson and installing it through Recovery but that failed too. Busybox won't install because it says SU is screwed-up or I don't have root..
I was just hoping to find some ROM that could take advantage of this large screen, out of the box it boots and looks like a tablet for the sight-impaired (no offense) because all it does is display these huge icons and huge text (even after reducing text size to small). From all that I have seen today it looks like nobody is developing for this device. I guess we should be happy that we got 4.2.2 out of the box, at least we're ahead of most others..
Anyone have any ideas???
Chris R.
Click to expand...
Click to collapse
It has a version of SU in xbin, but that doesn't mean that it is rooted really....
I have tried to get ADB to work, but so far no luck with that. I believe that I could get root to work if I could get ADB to work, but that is just a circular argument.
As to the screen, I use an alternate launcher. Apex in my case. It allows me to set the grid size and scales the icons to fit. Others like other launchers better, but I prefer Apex and purchased the pro version.
All around I like it, even without root. Still, I would like to be able to use GL to SD, Titanium Backup, and the host of other root reliant apps I normally install to get around certain deficiencies.
I'm also trying to root this device.
After a lot of digging, it looks like the su in xbin has different permissions (at least as far as I can tell), when comparing it to the su in my rooted s3. I used root checker pro. The permission of su on my s3 is -rwsr-sr-x root root 113036, while the permission for su on my SN14T71 is -rwsr-sr-x root root 67080.
The funny thing is root checker pro says that root ownership is present and is properly configured. The only thing I can think of is the permission isn't set right.
Now without adb (which I can't seem to get to work either, even though there is a debugging option in the android settings), I don't see a way to change the permissions. Anyone have any ideas?
My usb file transfer doesn't even work on this device. When I try to use usb to transfer files it remounts the internal memory and crashes the tablet, and I have to shut down and reboot to fix it.
I think that they messed up remote usb access period, and that might be why adb doesn't work.
I can use usb file transfer just fine. It only works through the OTG port, not the "regular" port, or whatever you want to call it. In fact, I have no idea what the regular port is even there for, if file transfer only works through OTG. My computer (running ubuntu 12.04) doesn't even detect the tablet using lsusb when connected to the non-OTG (regular) port.
And yet, ADB doesn't work with either port. They definitely did something wrong here, I just can't figure out what.
I can only transfer files via the OTG port and a flash drive. Connecting to a computer, and I have tried windows 7/8/8.1, only causes it to crash. We may only be able to hope that it is fixed in the next update...
Both external usb storage (OTG) and my computer work fine using the OTG port. Still can't figure out what the other port even does right now.
Are they still going to release updates? Hannspree's "news" section hasn't even been updated since 2012.
Ha. Your guess is as good as mine...
It is still my favorite tablet though. The Price/Performance ratio is good, and I love the huge screen even if I have to use the upside down tablet trick for better viewing angles. Mine does have the overheating bug though, which is primarily what causes crashes and wifi failure...
Rooting Hanspree SN14T71
I hope this helps.
I am usually a lurker and don't post but I wanted to pass this info along.
I was able to root my Hanspree SN14T71 by installing Mobogenie.
Install the Mobogenie PC App from mobogenie.com/en-us/download.html
then download the ADB drivers from here mobogenie.com/drivers-download.html
Put tablet into debugging mode.
Connect to pc then run the Mobogenie PC app click on the My Phone Icon in the upper left and from there you should be able to click the OneClick Root icon and root your SN14T71.
I have verified root access and have installed and run apps that require the tablet to be rooted.
Try at your own risk but this did work for me.
Good luck.
I've only had it for a few days actually, so I really haven't had enough time to figure out what all of it's quirks are. I actually got it to hang up on my fridge for the calender, shopping list, recipes, pandora, etc. It's attached using velcro so I can take it off if I need to.
Well I guess I'll work on getting it rooted occasionally when I feel like it, unless someone cracks it before me.
EDIT: I'll try that out wcbellaz. I'll report back if it works.
So I tried the one click root with mobogenie, and while it definitely did something, it didn't give me root access. Using the one click root, it actually moved the su from /system/xbin to /system/bin, but still doesn't give me permission to use su. Setuid attribute is there, and the root ownership is there, so theoretically, I should be able to use su. Then again, I should have been able to with the original su file, which also has setuid and root ownership.
One thing that is strange when comparing it to my rooted galaxy s3 is under the "root user is and group id status" in root checker pro, the contents are different. On the hannspad, it says the su binary isn't found or isn't operating properly. On my GS3, it says the uid and gid are both root.
When I unroot it with the one click root, it removes the su file entirely.
So I know this mobogenie app can in fact get root privileges, as it did mess with the su file. I just wish I knew how it was doing it so I can do it myself.
Masterjuggler said:
So I tried the one click root with mobogenie, and while it definitely did something, it didn't give me root access. Using the one click root, it actually moved the su from /system/xbin to /system/bin, but still doesn't give me permission to use su. Setuid attribute is there, and the root ownership is there, so theoretically, I should be able to use su. Then again, I should have been able to with the original su file, which also has setuid and root ownership.
One thing that is strange when comparing it to my rooted galaxy s3 is under the "root user is and group id status" in root checker pro, the contents are different. On the hannspad, it says the su binary isn't found or isn't operating properly. On my GS3, it says the uid and gid are both root.
When I unroot it with the one click root, it removes the su file entirely.
So I know this mobogenie app can in fact get root privileges, as it did mess with the su file. I just wish I knew how it was doing it so I can do it myself.
Click to expand...
Click to collapse
That is really odd. I just got my Hannspad in the last 3 weeks. When I would run Root Checker it said the device was not rooted. I have heard some say that the device would report as rooted but in fact was not.
If there is anything I can do to help let me know.
I am pretty much a novice at this but I had to root my Hannspad because I did have enough space in memory left for apps, and needed to install Link2SD. In my opinion the only major drawback to this device is the 1GB memory. But for the $226 that this tablet was offered on Amazon was too good a deal to pass up.
Tried Mobogenie, and it seemed to install the correct driver and the driver pack was not needed - I had already started the install on the drivers though...
Sigh...
Got root, it uses a root app that I have never heard of - Kinguser - so I mistakenly installed SuperSU, which then asked me to update the superuser binary...
I am now in the process of restarting to find out if I messed up my root access.
Sigh...
Update:
Apparently I didn't lose root, so I have installed some of my root requiring favorites to see how they work.
The oneclick seems to update the su in xbin, and they put a link to it in bin with full permissions.
I have tried three apps that successfully report gaining su permissions, Root Explorer, Titanium Backup, and GL to SD.
I want to try the move updates to system option in TB, to free up some space, but I am currently too chicken.
Sigh...
Whelp, Titanium Backup works anyway...
Update 2:
I installed SuperSU ( re-installed it actually ) and did the normal binary update. Then I uninstalled Kinguser manually by using Root Explorer to delete its apk in SYSTEM ( superuser ). Then I restarted and deleted all traces of Mobogenie and its daemon as they were slowing down my tablet, and the daemon died hard ( I can imagine that it was tied into all sorts of things ).
I have confirmed that I still have root access, and I just didn't like all that Mobogenie stuff on my tablet.
Happy now
RageAgain said:
Tried Mobogenie, and it seemed to install the correct driver and the driver pack was not needed - I had already started the install on the drivers though...
Sigh...
Got root, it uses a root app that I have never heard of - Kinguser - so I mistakenly installed SuperSU, which then asked me to update the superuser binary...
I am now in the process of restarting to find out if I messed up my root access.
Sigh...
Update:
Apparently I didn't lose root, so I have installed some of my root requiring favorites to see how they work.
The oneclick seems to update the su in xbin, and they put a link to it in bin with full permissions.
I have tried three apps that successfully report gaining su permissions, Root Explorer, Titanium Backup, and GL to SD.
I want to try the move updates to system option in TB, to free up some space, but I am currently too chicken.
Sigh...
Whelp, Titanium Backup works anyway...
Update 2:
I installed SuperSU ( re-installed it actually ) and did the normal binary update. Then I uninstalled Kinguser manually by using Root Explorer to delete its apk in SYSTEM ( superuser ). Then I restarted and deleted all traces of Mobogenie and its daemon as they were slowing down my tablet, and the daemon died hard ( I can imagine that it was tied into all sorts of things ).
I have confirmed that I still have root access, and I just didn't like all that Mobogenie stuff on my tablet.
Happy now
Click to expand...
Click to collapse
Awesome.
You lost me on the binary stuff.
In your opinion should I uninstall the Kinguser as you did and install SuperSu. there seems to be no difference to me in performance after the Mobogenie root. I really don't want anything on this tablet other than the stuff I have to have.
wcbellaz said:
Awesome.
You lost me on the binary stuff.
In your opinion should I uninstall the Kinguser as you did and install SuperSu. there seems to be no difference to me in performance after the Mobogenie root. I really don't want anything on this tablet other than the stuff I have to have.
Click to expand...
Click to collapse
The Kinguser seems to work fine, I just like using what I am used to and I couldn't find much info on Kinguser superuser app ( in english anyway ) so...
It does have a lot more configuration options than SuperSU, which could be a good thing. Your guess is as good as mine...
Hold the phone. Kinguser? I have never heard of this, nor has it been installed on my tablet by the one click root.
I did install SuperSU and tried updating the binary (without success) before trying mobogenie to see if I could get it to work. This wouldn't have screwed me over in any way, would it?
EDIT: Just to be sure, you both are running the latest OTA update, right?
Masterjuggler said:
Hold the phone. Kinguser? I have never heard of this, nor has it been installed on my tablet by the one click root.
I did install SuperSU and tried updating the binary (without success) before trying mobogenie to see if I could get it to work. This wouldn't have screwed me over in any way, would it?
EDIT: Just to be sure, you both are running the latest OTA update, right?
Click to expand...
Click to collapse
Version 1.1.4 dated 11/23/2013
I used a laptop running windows 7, and installed Mobogenie ( I also, perhaps unnecessarily, installed the adb driver pack ). I then connected my tablet and Mobogenie reported a connection - it reported the available memory both internally and on the sd card and it could see my installed applications, after which I used the one click root. The Mobogenie app and daemon were installed along with an updated su and the Kinguser superuser app.
As far as I know trying to install SuperSU previously shouldn't have any effect on the process since I did that too.

Strange Root behavior - New apps can't get root

I have had my tablet rooted since I got it pre-4.2.1. I was trying to setup TWRP as I finally decided to ROM my device and ran the unlock tool.
However, once I got past that and tried to use goomanager and TWRP manager, I realized apps were not being provided root any longer. However, the old apps that were approved in Superuser continue to get root and think that they have root, such as Titanium Backup, SManager, ES Explorer, etc. They continue to function as expected. However in SuperUser the logs have not updated in quite a while.
I've done several steps and reviewed a few related threads. Changing the prompt settings have not done anything, and I've tried several combinations of setting it to allow, setting it to prompt, rebooting etc. To confirm root is actually working I ran SManager and ran /system/bin/su which does work, and causes SuperUser to show new root access. Along the lines, I've nuked my dalvik cache using SManager and rebooted.
However, nothing else updates the logs, and new apps do not get root. Based on some other thread, I used voodoo OTA rootkeeper to remove root and then ran motochopper. Root came back, but continues to have the same behavior. SuperUser is unable to update itself, although it does show the binary as up to date. When I try to run an update anyway, it fails at the getting root step. SuperSU, rootchecker, android root toolkit all fail.
I am hoping I can figure out how to fix this, even though I unlocked the tablet, I'm traveling and not in a position to flash in TWRP. Since running SU works and previously approved apps also work - I think there is someway to restore full root capabilities. Any suggestions are appreciated.
ASUS Transformer Infinity TF700 - rooted/stock
Motorola ATRIX 4G - Rooted/Currently Stock/No longer in use - anyone need a guinea pig?
Motorola ATRIX2 - vanilla
ASUS Transformer TF101 - now vanilla and given to the wife
Really I swear I've had lots of roms on these devices at other times.

Categories

Resources