Database Info

Stock 2.1 rom rooted ROM Manager won't FIX Permissions

I searched and got on IRC and can't get a fix for this. WHen i try to use the Fix permissions option in ROM Manager Premium i get the following error.
"error occurred while attempting to run privelaged commands"
I checked superuser and ROM Manager is in there so i selected "forget" then rebooted and tried "fix permissions" again. I got the promp to allow SU and then the error.
Any idea how i can fix this? Is this a bug or a isolated problem?

Not sure if it is related or not but I had to same problem until I bought the full version off of the market.
Maybe it's part of the extended functionality?

As I noted I have "Rom Manager Premium" I don't think it's related anyway.

Just found the answer to this (as I too was having this problem). See the link below:
http://androidforums.com/899973-post26.html
It has to do with busybox not installed in the correct place.
One more thing: Make sure that busbox is set to "755" so that it can execute.

Thanks
sw99 said:
Just found the answer to this (as I too was having this problem). See the link below:
http://androidforums.com/899973-post26.html
It has to do with busybox not installed in the correct place.
One more thing: Make sure that busbox is set to "755" so that it can execute.
Click to expand...
Click to collapse
Thanks for the link to the fix!

I am unable to get the busybox file to copy from the /data.... directory into the /system/bin/ directory. Any ideas?

jtoole1 said:
I am unable to get the busybox file to copy from the /data.... directory into the /system/bin/ directory. Any ideas?
Click to expand...
Click to collapse
did you mount the system partition prior to trying this?

I'm also having an issue moving the file using root explorer. Any other ideas?

the_grobe said:
I'm also having an issue moving the file using root explorer. Any other ideas?
Click to expand...
Click to collapse
Yeah, same here. My problem is that I've never used Root Explorer before. At the top it says mounted as r/w (in the /system/bin directory) , but it won't copy the file using the Root Explorer program. When I click [Paste] it doesn't give me an error, but when I go and check the directory, the file is not there. I even tried refresh. Any ideas?
UPDATE: I have not solved the problem yet, but I did notice that the /system/bin directory that I am trying to copy to says "0K bytes available," which is probably why it won't copy. So I guess my (no copy) problem is due to my lack of understanding of the file structure of the DI.

UPDATE: I finally got it working. Here is what I did.
1. Boot phone into recovery
2. Push busybox from /sdk/tools folder to sdcard
Code:
adb push busybox /sdcard/busybox
adb shell
3. Installed busybox to /system/xbin
Code:
$ su
#export PATH=$PATH:/system/bin
#cd /system/xbin
# cat /sdcard/busybox > busybox
# chmod 06755 busybox
# busybox --install -s /system/xbin
# rm /sdcard/busybox
# exit
$ exit
4. Booted up phone, and ROM manager fixed permissions as per request.
Hope that helps.

Thanks. I appreciate your feedback. But it looks like I wasted my money again on a useless program like "Root Explorer." I was hoping that I wouldn't have to do all of that command line crap anymore after having rooted.
Does anyone know if there is a file manager out there that will push/pull files via cut/paste rather than using a seperate computer with a command line interface?

I don't think that there is going to be a program like that until we've got full NAND unlock.

the_grobe said:
I don't think that there is going to be a program like that until we've got full NAND unlock.
Click to expand...
Click to collapse
Is someone working on that? I believe the facts are, that the Unrevoked team knows how to do it...but they won't give us the means to do it. Probably because they think we'll shoot ourselves in the foot...and blame them...and they're probably right!

I can not do the cat command it tels me Cant create busybox, read only file system.
Any ideas????????????????

when i was modding widget locker i was using linda file manager free to cut and paste out of the system folder im gonna try it right now to fix this problem ill let u know if it works

[Resolved] HANNSpree HSG1279 root and recovery!!! [Updated 01/28/14]

Updated OP with solution, many thanks to @fipsy for the final solution, here is his post for those that need help rooting this device: (UPDATE: Root for 4.2.2 at the end of the post)
fipsy said:
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. So you have to reconstruct my links yourself into your browser)
As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.
The necessary USB drivers for the device are found here: http://yadi.sk/d/54lX5c2O386XU
They only work with Windows 7!
After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
Copy it to your /sdcard. Then continue with adb shell:
Code:
$ su
# cd /system/xbin
Mount the system partition read/write:
Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system
Rename the original binary for later use (if something fails):
Code:
# mv su su-orig
Copy the binary to the xbin folder:
Code:
# busybox cp /sdcard/su ./su
Change the permissions:
Code:
# chmod 6755 su
Mount the system partition read-only and exit:
Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit
Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Click to expand...
Click to collapse
CUSTOM RECOVERY FINALLY POSSIBLE!!! Again, many thanks to @fipsy, here is his post:
fipsy said:
I finally made it! :laugh: Here is a working CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279).
I didn't fully test it but the backup function works. Also mounting and unmounting partitions works as well as the adb shell which is very important if the device is bricked and doesn't boot anymore.
Before connecting to the device via adb shell it is necessary to mount the /system partition (menu "mounts and storage") because otherwise /system/bin/sh cannot be found by adb shell.
The CWM recovery by default stores it's backups on the external SD-Card. The benefit is that the backup can easily be plugged out and stored apart from the device. But the recovery is also able to restore backups from the internal sdcard. Those backups can be made online on a running android system by using apps like "Online Nandroid Backup" and "Nandroid Manager". The benefit is that it's not necessary to reboot the device before backing up and you can keep on working.
There is one problem when creating backups in CWM Recovery: The date/time of the backup is always set to 1st of January 1970 due to a missing backup battery in this device. Look here: http://tau.shadowchild.nl/attn1/?p=341. So if you want to make backups with accurate timestamps you would have to set the actual time of the device using adb shell: Start adb shell and enter:
Code:
/system/xbin/busybox date -s "YYYY-MM-DD hh:mm:ss"
before making the backup.
To cut a long story short: Download the CWM-Recovery here: http://yadi.sk/d/ArprqzfFFWvy4 and flash it to your (rooted) device. How to do this:
Copy the file cwm-recovery.ima to your internal sdcard.
Either connect via adb shell and enter su
or run a Terminal Emulator and enter su
then enter
Code:
cat /sdcard/cwm-recovery.ima > /dev/block/acta
and you're done! Have fun! Comments are appreciated!
Perhaps someone likes to create an update.zip from it?
Edit (01/28/2014): There is a new version 6.0.3.3. Look here: http://forum.xda-developers.com/showpost.php?p=49835135&postcount=283
Edit (05/04/2014): There is a new version 6.0.3.3.a. Look here: http://forum.xda-developers.com/showpost.php?p=52416205&postcount=492
Click to expand...
Click to collapse
ROOT for new OTA 4.2.2 update:
fipsy said:
Good news for germany: The rollout began tonight! I just got the update to Android 4.2.2! :laugh:
Some people asked for the upgrade file to manually update from the recovery. Here it is: http://yadi.sk/d/igsBGsAjFpLsL
Edit (01/13/2014): Seems this update only works on devices with special G-Sensor hardware (KIONIX 3-axis Accelerometer).
@ig6677: There you will also find the META-INF you wanted.
For your information: After my update to Android 4.2.2 root has gone on my device! I expected this. All Apps that need root don't work anymore. I don't know what you did that root was still there after the update...
Furthermore in /system/xbin there is no su file anymore. Also my CWM Recovery has gone and was replaced by the Stock HANNspree recovery!
But whats new: If you connect to the device via adb shell you immediately have superuser rights! No su is needed for this anymore. So it's possible to restore the CWM Recovery using cat.
If you adb push the 3.1.1 su binary from your pc to the /sdcard on your device and after this execute my commands in the first posting of this thread the apps have su rights with superuser.apk again. But you will not be able to add new programs to the superuser app (if a new app requests superuser rights there is no popup). So this is no solution.
The Superuser App is not able to grant superuser rights on android systems > 4.1.1, but the App SuperSu is! So download the SuperSU ZIP from here: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Then copy it to your sdcard and install it using the Recovery. Voila! Everything works again!
Another issue: The Huawei E1750 Surfstick is not detected anymore. On 4.1.1 it was no problem to surf using this stick. But I think this is one of the "great features" of the new android versions...
Click to expand...
Click to collapse
New recovery version!
fipsy said:
:victory: Here it is: The new version 6.0.3.3 of CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279)
Beside some minor bugfixes the main benefit of this release is that there are no more errors when trying to restore the .android_secure folder. So the "dirty" workaround to restore this folder is not necessary anymore.
The .android_secure folder is also automatically restored together with the data partition when selecting "data" from the "advanced restore" options.
http://yadi.sk/d/OmsYk6TIGsBsB
Information on how to install you will find here: http://forum.xda-developers.com/showpost.php?p=49166546&postcount=133
Cheers, Volker
Click to expand...
Click to collapse
My original question:
Just bought this tablet on Cybermonday for a really good price, but can't find a way to root it for the life of me...
Main problem has been I can't see it using ADB (v1.0.31), always list no devices even with the latest generic Google ADB driver, which shows fine on device manager.
Tablet comes with Android 4.1.1 and no extras, is just a plain version of android with Play market and ES File Explorer pre installed and have access to android stock recovery.
Any ideas?
Also, just in case I start messing with the tablet, Any way I can backup the stock system just in case?
Thanks.
Update:
More info on the tablet...
Model name: SN1AT71
Hardware (According to CPU-Z): gs702a
Board: full_gs702a
Click to expand...
Click to collapse

Omegadrive said:
Just bought this tablet on Cybermonday for a really good price, but can't find a way to root it for the life of me...
Main problem has been I can't see it using ADB (v1.0.31), always list no devices even with the latest generic Google ADB driver, which shows fine on device manager.
Tablet comes with Android 4.1.1 and no extras, is just a plain version of android with Play market and ES File Explorer pre installed and have access to android stock recovery.
Any ideas?
Also, just in case I start messing with the tablet, Any way I can backup the stock system just in case?
Thanks.
Update 1:
More info on the tablet...
Model name: SN1AT71
Hardware (According to CPU-Z): gs702a
Board: full_gs702a
Click to expand...
Click to collapse
Update 2:
Found that this tablet is practically the same as the Ainol Novo 10 Hero (don't know if version 1 or 2 thou)
So looking in Google found a thread that has modded ADB drivers and following the instructions managed to get ADB to find the device.
Now to keep experimenting

Omegadrive said:
Update 2:
Found that this tablet is practically the same as the Ainol Novo 10 Hero (don't know if version 1 or 2 thou)
So looking in Google found a thread that has modded ADB drivers and following the instructions managed to get ADB to find the device.
Now to keep experimenting
Click to expand...
Click to collapse
Update 3:
After trying over 20 generic rooting methods I come back defeated, 6 hours of testing and nothing. :crying:

I also have picked up 2 of these devices (1 for me and 1 for my wife). I have tried every method I can find to root this, inclicking mutliple one click solutions, apps that are suposted to root, etc. and none of them seem to work, I think the reason why is because the device is being reconized as allready being rooted, SuperOneClick, Framaroot, and Kingo all stated that it was allready rooted ..but apps will not install as if the device was truly rooted. Also geting "access denied" when trying to access the root folder..
Applications that require root will install because they think it has root, they also will prompt stating to give root access/permissions, but when accepting, they simply lock up because they can't access the root correctly.
anyways, I'm done trying for now.. if anyone has any other ideas, please speak up and let us know. thanks!

also have one of these
Temil2006 said:
I also have picked up 2 of these devices (1 for me and 1 for my wife). I have tried every method I can find to root this, inclicking mutliple one click solutions, apps that are suposted to root, etc. and none of them seem to work, I think the reason why is because the device is being reconized as allready being rooted, SuperOneClick, Framaroot, and Kingo all stated that it was allready rooted ..but apps will not install as if the device was truly rooted. Also geting "access denied" when trying to access the root folder..
Applications that require root will install because they think it has root, they also will prompt stating to give root access/permissions, but when accepting, they simply lock up because they can't access the root correctly.
anyways, I'm done trying for now.. if anyone has any other ideas, please speak up and let us know. thanks!
Click to expand...
Click to collapse
I picked up one of these also, I tried a few of the rooting methods you guys listed before finding this post. also no sucess, Would love to get this working bit better,because stock rom is a bit sluggish when it shouldn't be given the specs.

OK, kept trying and found some interesting stuff, first of all a screenshot with the tablet info:
{
"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"
}
Second, it seems the tablet is already rooted but the root is just dummy or the interface has been disabled with deny set as default for any application.
So the trick to root it must be a way to replace de su binary or change the default permission to allow.
Any experts have any idea how to achieve this?
Sent from my HSG1279 using xda app-developers app

I thought about buying this Tab. But if there is no working root-methode or costumROM ability thats a dealbreaker for me.
You told that this tab should be identical to the "Ainol Novo 10 Hero". I dont know if that is true, because in one forum some guy told, that the HannSpee is chargeable via the USB-Port, and afaik the Ainol is not. You have the Hannspee, can you tell me if it is chargeable via USB ?
Anyway, on the german Amazon-site there is a guy that claims that costum-ROMs are working on the Ainol
I will ask him how he managed that and perhaps you can try that on you device. But I dont know if he answers, because responds on Amazon-rewievs are not like those in forums (often never answered)
hope some nerd comes up with a nice plan to break into this device......non-rooted devices are s**t!
greetz gerd
Omegadrive said:
OK, kept trying and found some interesting stuff, first of all a screenshot with the tablet info:
Second, it seems the tablet is already rooted but the root is just dummy or the interface has been disabled with deny set as default for any application.
So the trick to root it must be a way to replace de su binary or change the default permission to allow.
Any experts have any idea how to achieve this?
Sent from my HSG1279 using xda app-developers app
Click to expand...
Click to collapse

revnu said:
I thought about buying this Tab. But if there is no working root-methode or costumROM ability thats a dealbreaker for me.
You told that this tab should be identical to the "Ainol Novo 10 Hero". I dont know if that is true, because in one forum some guy told, that the HannSpee is chargeable via the USB-Port, and afaik the Ainol is not. You have the Hannspee, can you tell me if it is chargeable via USB ?
Anyway, on the german Amazon-site there is a guy that claims that costum-ROMs are working on the Ainol
I will ask him how he managed that and perhaps you can try that on you device. But I dont know if he answers, because responds on Amazon-rewievs are not like those in forums (often never answered)
hope some nerd comes up with a nice plan to break into this device......non-rooted devices are s**t!
greetz gerd
Click to expand...
Click to collapse
Well, I deduced it was identical to the Ainol Novo cause at least the hardware specs are identical and the board and CPU are reported by CPU - Z to be the same one. Tablet layout is a little different thou.
Anyway yes, this one charges through the USB port, but really slowly, good enough to have the USB connected while using it and will not drain the battery, but on my last test it barely charged 5% in 3 to 4 hours of while using it.
Crossing my fingers you can get in contact with that guy and we can figure out how to root this ****er lol
Sent from my XT910 using Tapatalk

Omegadrive said:
Well, I deduced it was identical to the Ainol Novo cause at least the hardware specs are identical and the board and CPU are reported by CPU - Z to be the same one. Tablet layout is a little different thou.
Anyway yes, this one charges through the USB port, but really slowly, good enough to have the USB connected while using it and will not drain the battery, but on my last test it barely charged 5% in 3 to 4 hours of while using it.
Crossing my fingers you can get in contact with that guy and we can figure out how to root this ****er lol
Sent from my XT910 using Tapatalk
Click to expand...
Click to collapse
He answered me, that his Hero came rooted when he bought it and that he simply had to install CWM. He posted a link with iinstructions but I bet it wont help, because the HANNSpree cames with kind of a fakeroot.

revnu said:
He answered me, that his Hero came rooted when he bought it and that he simply had to install CWM. He posted a link with iinstructions but I bet it wont help, because the HANNSpree cames with kind of a fakeroot.
Click to expand...
Click to collapse
Unfortunately it didn't worked, kept failing at validating files when it was installing from default recovery.
Anyway, going to try another method, these are the steps I followed:
1) Get ADB working and recognized.
a) Download these modded drivers and extract them.
b) Do this to install them since the drivers are not signed:
run CMD as admin
bcdedit -set TESTSIGNING ON
reboot
install driver from device manager
bcdedit -set TESTSIGNING OFF
reboot
c) Go to %userprofile%\.android folder and if it doesn't exist create a text file named "adb_usb.ini" (no quotes and make sure INI is the extension, not TXT), open it and just add "0x10D6" (no quotes), save it
d) open CMD as admin
adb devices
Your device should be recognized at this point, this is what I got:
C:\>adb devices
List of devices attached
0123456789ABCDEF device
2) Will update post with new findings here...

How to root the device
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. So you have to reconstruct my links yourself into your browser)
As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.
The necessary USB drivers for the device are found here: http: //yadi.sk/d/54lX5c2O386XU
They only work with Windows 7!
After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http: //downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
Copy it to your /sdcard. Then continue with adb shell:
Code:
$ su
# cd /system/xbin
Mount the system partition read/write:
Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system
Rename the original binary for later use (if something fails):
Code:
# mv su su-orig
Copy the binary to the xbin folder:
Code:
# busybox cp /sdcard/su ./su
Change the permissions:
Code:
# chmod 6755 su
Mount the system partition read-only and exit:
Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit
Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker

Omegadrive said:
Unfortunately it didn't worked, kept failing at validating files when it was installing from default recovery.
Anyway, going to try another method, these are the steps I followed:
1) Get ADB working and recognized.
a) Download modded drivers and extract them.
b) Do this to install them since the drivers are not signed:
run CMD as admin
bcdedit -set TESTSIGNING ON
reboot
install driver from device manager
bcdedit -set TESTSIGNING OFF
reboot
c) Go to %userprofile%\.android folder and if it doesn't exist create a text file named "adb_usb.ini" (no quotes and make sure INI is the extension, not TXT), open it and just add "0x10D6" (no quotes), save it
d) open CMD as admin
adb devices
Your device should be recognized at this point, this is what I got:
C:\>adb devices
List of devices attached
0123456789ABCDEF device
2) Will update post with new findings here...
Click to expand...
Click to collapse
umm, instead of using custom drivers, why not simply use the newest android Drivers? confirmed they work and device is reconized correctly, as long as you "install official droid drivers" then change the "adb_usb.ini" to only include 0x10D6 device, same as your last steps, but using official drivers, instead of custom ones. Maybe it has something to do with the failures?
---------- Post added at 08:00 PM ---------- Previous post was at 07:53 PM ----------
fipsy said:
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. So you have to reconstruct my links yourself into your browser)
As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.
The necessary USB drivers for the device are found here: http: //yadi.sk/d/54lX5c2O386XU
They only work with Windows 7!
After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http: //downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
Copy it to your /sdcard. Then continue with adb shell:
Code:
$ su
# cd /system/xbin
Mount the system partition read/write:
Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system
Rename the original binary for later use (if something fails):
Code:
# mv su su-orig
Copy the binary to the xbin folder:
Code:
# busybox cp /sdcard/su ./su
Change the permissions:
Code:
# chmod 6755 su
Mount the system partition read-only and exit:
Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit
Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Click to expand...
Click to collapse
thanks for this info. I'll test it out tonight, and let you know.
one question though.. so are you saying that future updates of SU will not work? if we do this, should we also disable auto-updates? If the software does update, will it break our system.. or simply that we need to reload the SU over again, but the OS will open, just limited to "non-rooted" ? ??

fipsy said:
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. So you have to reconstruct my links yourself into your browser)
As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.
The necessary USB drivers for the device are found here: http: //yadi.sk/d/54lX5c2O386XU
They only work with Windows 7!
After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http: //downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
Copy it to your /sdcard. Then continue with adb shell:
Code:
$ su
# cd /system/xbin
Mount the system partition read/write:
Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system
Rename the original binary for later use (if something fails):
Code:
# mv su su-orig
Copy the binary to the xbin folder:
Code:
# busybox cp /sdcard/su ./su
Change the permissions:
Code:
# chmod 6755 su
Mount the system partition read-only and exit:
Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit
Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Click to expand...
Click to collapse
OMG!!! IT WORKED!!!
MANY THANKS!!!
Now have full root privileges woot!!! Tested with Titanium backup and ES File explorer they accepted root and got permission prompts :highfive:
I will update the OP with your instructions, they worked beautifully, MANY THANKS AGAIN!!!
Btw, Do you have any idea on which custom recovery may work and if the bootloader can be unlocked? (if it is locked, I can't see anything when booting into fastboot mode and Windows doesn't recognize the tablet at that moment, only shows unknown device)
I want to make a backup of the stock rom and start testing CM builds on it.

Temil2006 said:
umm, instead of using custom drivers, why not simply use the newest android Drivers? confirmed they work and device is reconized correctly, as long as you "install official droid drivers" then change the "adb_usb.ini" to only include 0x10D6 device, same as your last steps, but using official drivers, instead of custom ones. Maybe it has something to do with the failures?
Click to expand...
Click to collapse
The original Android drivers never worked for me, used latest version 8.0 and the device was not recognized for some reason, only the modded drivers worked to recognize the ADB device. Btw, I'm using Windows 8.1 Pro and had to turn off driver signature to get the ADB drivers installed, maybe the issue was Win8.1 itself, but oh well, at least now we have a solution. :laugh:

fipsy said:
Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Click to expand...
Click to collapse
Update: After giving permissions with Superuser I went ahead and installed my SuperSU Pro license, gave it root rights (told it NOT to uninstall the other root app on prompt) and installed as a system app from within the app itself, reboot and voila! still fully rooted and binary updated (it replaced the other Superuser on reboot). So yeah, su binary updates are possible now :victory:

is there any custom recovery to install on this tablet?

Temil2006 said:
umm, instead of using custom drivers, why not simply use the newest android Drivers?
Click to expand...
Click to collapse
This also was my first attempt but it failed. So I went the same way as Omegadrive did: I identified the device as a clone of the "Ainol Novo 10 Hero" and searched for appropriate drivers. I found the same ones as Omegadrive did. And they seem to be the only ones that are working.
Temil2006 said:
one question though.. so are you saying that future updates of SU will not work? if we do this, should we also disable auto-updates? If the software does update, will it break our system.. or simply that we need to reload the SU over again, but the OS will open, just limited to "non-rooted" ? ??
Click to expand...
Click to collapse
I don't know if future binaries will work. When I manually updated the su-binary within the Superuser App it definitely didn't work anymore. Maybe because the su was exchanged with an older version (3.0.*). But Omegadrive said that updates are possible. So I don't know at the moment. Be careful anyway! Normally there is no reason for updating fully working binaries. The su binary is never updated automatically. So you don't have to deactivate any auto-updates.
Cheers, Volker
---------- Post added at 03:34 AM ---------- Previous post was at 03:04 AM ----------
Omegadrive said:
Btw, Do you have any idea on which custom recovery may work and if the bootloader can be unlocked?
Click to expand...
Click to collapse
The recovery mode is activated by pressing "Volume down -" and at the same time pressing the on/off key for about 3 seconds. Then releasing it while keep on holding down the "Volume -" until the recovery menu appears.
I think it will be possible to adapt the CWM Recovery. Perhaps we can investigate together on that!? Here the recovery file system table (for nandroid etc.). I just sent it to Ameer Dawood, the developer of "Online Nandroid Backup", so that he may integrate it into his App.
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /mnt/sdcard vfat /dev/block/actj (null) 0
2 /system ext4 /dev/block/actc (null) 0
3 /cache ext4 /dev/block/acte (null) 0
4 /data ext4 /dev/block/actd (null) 0
5 /data_bak vfat /dev/block/actf (null) 0
6 /boot vfat /dev/block/actb (null) 0
7 /recovery vfat /dev/block/acta (null) 0
8 /misc emmc /dev/block/actb (null) 0
9 /mnt/sd-ext vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0

Oh nice, thanks for the help, I'm no programmer, just a tinkerer, I'm willing to test anything you throw this way lol
My main priority right now is to make a backup of the current rom and then look for a way to repartition the /data cause 1Gb for apps is way too low, specially when there are 13Gb free on /sdcard, as want to make it 4Gb for /data and rest internal. I'm assuming I have to install custom recovery for that, or can ir be done right now from ADB?
Sent from my HSG1279 using Tapatalk

If you want to store parts of the filesystem (like /data/app, /data/app-private, /data/dalvik-cache and libs) to the sd-card you probably will have to install a custom rom like cyanogenmod which supports additional partitions / filesystems on the sd-card (like ext2).
But you're right. The first thing to do before making any experiments is to make a full backup (nandroid) and be able to restore it from a recovery. So we first should investigate on that...

I just installed the CWM recovery for the Ainol Novo 10 Hero 2 for testing. The device started into the CWM recovery screen but then failed to mount some folders. The menu was working but most features were not functional. This means that the HSG1279 is *not* fully compatible with the Ainol Hero 2.
So we have to find another solution. I suppose it will be quite a lot of work to adapt the CWM recovery to this device...

[Emulator][Root][How-To] BlueStacks 0.9.x + pre-rooted 0.9.30.4239 image

This How-To briefly describes a way to manually root recent BlueStacks without any third-party apps. All you need is a linux distro (you can use VirtualBox virtual machine) and SuperSU CWM flashable. I won't go into much details, some little linux know-how is needed, but you can always google for what you don't understand, since the required steps are fairly simple. I also share a pre-rooted BlueStacks 0.9.30.4239 image for the lazy ones
This How-To assumes you already have an installed BlueStacks you wish to root, but make sure it isn't running. So, let's get started
1. Copy over UPDATE-SuperSU-v2.46.zip and BlueStacks Root.fs to your linux box: in Windows it is typically located at "C:\ProgramData\BlueStacks\Android\Root.fs". If you're using VirtualBox, I suggest you use a shared folder to copy the image over to the guest linux OS.
2. As root, unpack UPDATE-SuperSU-v2.46.zip and mount Root.fs as a loop device.
3. Now we need to copy over (as root) some of the extracted files to the mounted Root.fs:
arm/su --> android/system/xbin/su
arm/su --> android/system/xbin/daemonsu
arm/supolicy --> android/system/xbin/supolicy
arm/libsupol.so --> android/system/lib/libsupol.so
common/Superuser.apk --> android/system/app/Superuser.apk
4. Since there's no init.d structure in BlueStacks, we need to edit android/system/etc/init.sh: at the buttom of the file find these lines:
Code:
init|"")
do_init
;;
esac
and insert one line after 'do_init':
Code:
init|"")
do_init
/system/xbin/daemonsu --auto-daemon &
;;
esac
5. Unmount the loop device and copy the modified Root.fs over to your BlueStacks Android dir (typically, "C:\ProgramData\BlueStacks\Android" in Windows). You may want to make a backup of the original file just in case.
6. Start BlueStacks and launch SuperSU via Play Store: it will prompt for upgrading su binary --- choose the normal way and restart BluseStacks upon completion.
7. That's it, you're rooted! Now you may wish to install a proper launcher (like Nova Launcher) if you have not done so already.
Now, as promised, you can grab pre-rooted BlueStacks 0.9.30.4239 Root.fs from here:
https://www.mediafire.com/folder/bc7hjf0a8lgnq/BlueStacks_Root
Stop BlueStacks, copy Root.fs over to your BlueStacks Android dir, and start BlueStacks. In case your current version is incompatible with the image, try BlueStacks-ThinInstaller_0.9.30.4239.exe from the link above. I'm not sure whether this ThinInstaller will download the proper data when newer version is released, so no guarantees here, you may still need to do it manually at some point in the future unless I maintain the Root.fs actual.

200+ people downloaded rooted image already, and not a single response yet. Some feedback would be appreciated, you know

Serkenar said:
200+ people downloaded rooted image already, and not a single response yet. Some feedback would be appreciated, you know
Click to expand...
Click to collapse
Thanks, worked perfect for me

thanks replace root.fs works for me, was using 9.27.5408

mac-duff said:
Thanks, worked perfect for me
Click to expand...
Click to collapse
netsee said:
thanks replace root.fs works for me, was using 9.27.5408
Click to expand...
Click to collapse
Great, I'm glad that it works. Thanks for the feedback!

link for zip is broken

how to copy over busybox config file? (completelinuxinstaller)

Hello everyone.
I have been wanting to get to grips with linux for a while now and decided linux decided to try completelinuxinstaller as i was having some problems with linux deploy.
i set up everything as the app asked. Downloaded .img files, extract, rename file and launch.. but in the android terminal i get a error which said:
chroot: can't execute '/root/init.sh': Permission denied
After days of searching and trying minor fixes i got no where until i found a list of instructions on how to fix this error.
(This error is becoming common on Samsung devices running android version 4.4.2, and can be expected to happen with some other devices, or newer versions of android. Although I haven't yet found the exact cause of the error, an effective workaround has been found:
The error seems to be coming from something in the busybox executable installed by the Complete Linux Installer app; many have reported that using other versions of busybox removed this problem, and the following version (free download on Google Play) has been confirmed to work: BusyBox
After using that app to install an updated busybox binary, simply copy the new binary over the existing busybox binary at /data/data/com.zpwebsites.linuxonandroid/files/busybox
Finally, in a rooted terminal window, type chmod 0755 /data/data/com.zpwebsites.linuxonandroid/files/busybox (see the more detailed instructions in the How do I install the most up-to-date version of bootscript.sh on my device? section of this FAQ)
Now you should be able to start linux using your Complete Linux Installer app on your device.)
But the problem is no matter what explorer i use i am not able to find the busybox config file. Where they said it would be doesnt exist. Even if i go to android/data its not there. Just the .com for all other apps. do you know where the busybox might be ?. On the busybox installer it says it is in /system/xbin but again i cant find it on my device.
And if i may chew your ear off for one more moment. How can i change the .config file ?
Thank you for your time

[Megathread]Root Fire HD 10 (7th Gen 2017)

FOR FIRE HD 10 (7th GEN, 2017) ON 5.6.0.0 ONLY
Seems like this is a tradition so I will put this on here.
Update 4: 2018/1/14, Offline rooting method by retyre (If no new method comes out, this will be the final update)
Update 3: 2018/1/1, Minor text fix
Update 2: 2017/12/31, New rooting method by bibikalka.
Update 1: 2017/12/28, Added more content
Code:
###Disclaimer###
I am not responsible for the potential damage that will be done to your tablet, such as boot looping and bricking.
Your warranty might be void by doing the following steps.
YOU are choosing to make these modification.
Looks like these methods doesn't work for Fire HD 8 (7th GEN, 2017)
Reason to start this thread
The topic was started by ztrund in this thread and we ended up with a pretty messy thread, which makes people really hard to locate the exact tutorial post. So I think it should be a good idea to start a new thread.
Note: This thread doesn't work for HD 10 (7th Gen) anymore because root access is temporary and it can't survive after a reboot. As a result, don't follow the exact steps on that thread.
Special thanks to strund, DragonFire1024, Blaiser47, mistermojorizin, UROMEGAX, retyre, bibikalka and countless people who helped, discussed and contributed in the original thread.
By the way, please correct me if there is any problem or mistake.
Some useful posts
1. The first detailed tutorial is located in #221 in the original thread. mistermojorizin provided the method and adb shell history.
2. #233 in the original thread. UROMEGAX provided a detailed guide of the method.
3. #304 in the original thread. I provided a more coherent step by step guide.
4. #248 in the original thread. retyre provided a different way to root the tablet. (Blaiser47 wrote that it's easier for him)
5. Easier Way to Root Fire HD 10 used a different approach by bibikalka. (Looks like new method is easier to do) (For legacy method go to post #2)
6. Offline Rooting Method by retyre
After getting root access
1. Xposed & FlashFire posted by retyre
2. tweaks/apps/modules/hacks/optimizations started by razers7t8

New method
Easier Way to Root Fire HD 10 by bibikalka.
Offline Rooting Method by retyre
Legacy way
You need the following things in order to proceed:
1) adb (Available Here)
2) Kingoroot PC version (Available Here)
3) Kingo.to.SuperSU.zip (can be found here in the attachment of the post)
Preparation work:
1. Turn on USB debug mode and "allow third party app to install" on fire HD 10
2. Update Kingoroot to the latest version
Note: There will be a small grey box on the update pop up page. It is up to you whether to uncheck that box or not. I don't think that will affect the following process.
3. Connect your fire HD 10 with your PC.
4. Unzip "Kingo.to.SuperSU.zip". Copy the folder to your internal storage on tablet.
Note: In root explorer the directory is /storage/emulated/0
Let's start:
1.- Install supersu (ver 2.82) on the fire and root file explorer.
2.- Use Kingoroot to root
3.- Open the adb shell and start to type "su" while Kingoroot is rooting (You can also wait until it's done, then type su to proceed)
Code:
[email protected]:/ $ su
Note: Do not type "adb shell su" because you won't be able to type any command once the # appear. The correct way is to type "adb shell" first then start typing "su"
4.- once the # appear i did # mount -w -o remount /system
5.-Uninstall the Kingo super user app normally (Do not choose to unroot in Kingo super user app)
6.- # cd /data/media/0/Kingo.to.SuperSU
7.- # cp ./su /system/xbin/daemonsu (no error was given in my situation)
8.-# chmod 0755 /system/xbin/daemonsu
9.-# daemonsu -d &
10.-# cp ./su /system/xbin/su
11.-# chmod 0755 /system/xbin/su
12.-# rm /system/xbin/supolicy
13.-# rm /system/bin/install-recovery.sh
14.-# rm -rf /system/usr/iku
15.-# rm -rf /sdcard/Kingroot
16.-Open Supersu (and get the Su occupied error)
17.-setting > reinstall (It is not rebooted)
18.-Install Supersu (ver 2.79) and open it
19.-Supersu ask the user to update binary (I tried to update the binary but failed, nothing happened, didn't reboot)
20.-setting > set supersu as a system app (Mine rebooted immediately after doing this step)
21.-Go to google play to launch Supersu (Don't know why the Supersu icon is not shown in the Fire Launcher so this is an alternative way to open Supersu)
22.-setting > set grant as default access
23.-Then (not sure if a reboot is required here) I received a notification from Supersu and it ask me to update binary
24.-Click the notification to update binary and it should work.
Not sure whether it will work or not if SuperSU (ver 2.79) is used in the beginning of the guide.

Personally the method posted here seems simpler and makes more sense to me.
https://forum.xda-developers.com/hd...re-hd-10-7th-generation-t3718629/post74940137
No need to mess with two versions of supersu. After you have root you can just update supersu and binaries to the latest.
I also do not think there is any need to start adb while kingoroot is rooting. It is fine, and maybe better to prevent errors, to just wait until it is done.
I would recommend one always go back to a clean system by sideloading the official Amazon 5.6.0.0 .bin and do not fully set up or connect to the internet until you have rooted. To skip Amazon set up, just select a wifi and enter the wrong password. Then hit back and it will let you skip. May need to do it a few times.
Make sure to say in the op to copy the kingo folder with the files to your SD card storage and clarify that this is the emulated SD. Implied but for newbies just saying you need to have it and not saying where could be confusing.
After you root, if you want the latest updates, at least as of a day or so ago you can still update officially via device options, system updates. But be careful as at some point doing this may remove root if Amazon pushes more updates. To this point I strongly encourage everyone who roots to keep a copy of the current 5.6.0.0 .bin in case you need to recover. If Amazon updates their website with a new updated os, this version may be gone.
Another note, if you are using the fire launcher (default) and new apps are not showing up, just go to manage apps and find the system app called Home Pages. Force stop it and see if that fixes it. If not, go back and force stop and clear data. That should make it work.
I'll add more as I think of things and as this thread evolves.

why do I have problems with the :
... cd /data/media/0/Kingo.to.SuperSU command
and the ... cd /sdcard/Kingo.to.SuperSU command
Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?

Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?
Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.
Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
C:\ADB>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
1|[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
Click to expand...
Click to collapse
{
"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"
}

bakshi said:
Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?
Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.
Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
Click to expand...
Click to collapse
I'll try to answer as much as possible.
First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.
Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.
For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------
davidinfoman said:
why do I have problems with the :
... cd /data/media/0/Kingo.to.SuperSU command
and the ... cd /sdcard/Kingo.to.SuperSU command
Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
Click to expand...
Click to collapse
Use adb and explore your devices directories. CD to get to a directory, ls to list things in the directory. It shouldn't matter how you get it onto your fire, but it needs to be unzipped. It also doesn't matter where you put it as long as you adjust the commands accordingly. Maybe try the downloads folder?

Thanks for your quick reply, I'll do this now!
UPDATE: Your advice worked! Thanks for clarifying that we should do this with a factory reset and should use Kingoroot on the PC.
Blaiser47 said:
I'll try to answer as much as possible.
First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.
Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.
For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
Click to expand...
Click to collapse

Part of my problem was seeing written many times ... put files on SD card, and I thought we had to have an external SD card put in the tablet. ( I have been running with that "false IDEA" for a couple of days until an hour ago.
No! SD card just refers to location that is on Fire Tablet itself. The ls command helped me a lot. Others should be aware of this.
I thank Blaiser47 for pointing that out. I am getting much further so far, following the advice in this thread.
Thank you oscarcx for starting this thread. Hopefully you can watch over it, and help correct our errors and giving helpful pointers.
Thanks everybody. I feel better now because the roadblock I hit, has been overcome, now for the other steps in the process.

Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.
Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.
5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.
6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.
7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.

manaox2 said:
Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.
Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.
5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.
6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.
7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Click to expand...
Click to collapse
manaox2
Thank You! Thank You! Thank You!
You are the man!
Only those of us that have been frustrated with this process can appreciate your KEEP IT SIMPLE approach to this!
Not sure why the other BIG thread on this couldn't do a step by step like you just did!
You listed the steps that were screwing around with me the last couple of days.
Finally it is ROOTED! Yeah!

Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?

Has anyone tried this method with HD 8 2017 ?

dusty23007 said:
Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?
Click to expand...
Click to collapse
1. You can get it from Google Play or get it from any liable third party app store.
2. If you get it from any liable third party app store, place it directly in the internal storage so you can install it in es file manager.
3. I remember seeing a post about how to save the bricked device in this forum. You can try to follow that post if your tablet got bricked.

YEAH!!!
rooted baby!!!! now can i get rid of the home tabs?
never mind... i disabled fire launcher

Silly question perhaps, Do I need to reset the device before attempting this?

Guys, how about HD8 2017 ?

wikke said:
Silly question perhaps, Do I need to reset the device before attempting this?
Click to expand...
Click to collapse
It is recommended but may not be required

hacker-on said:
Guys, how about HD8 2017 ?
Click to expand...
Click to collapse
As reported in the original long thread, it doesn't work on Fire 7 or Fire HD8.

my .02, i like these instruction by @retyre. Easy peasy when I had to re-root. mostly just posting here for my own reference, hope it's ok.
retyre said:
I have done this with success multiple times over the last day, so try this and report:
1. Start with a pristine /system (adb sideload update .bin if you can).
2. Root using KingoRoot as usual; confirm su usage in adb shell.
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps (incl. SuperUser) from the Apps page on your Fire's Settings.
5. Confirm su and daemonsu are in /system/xbin/:
Code:
cd /system/xbin
ls -al
If not, copy them to /system/xbin/ as in step 3.
6. Copy SuperSU 2.79 .apk (other versions might work, but this is the one I have tried) to your tablet and install.
7. Open SuperSU and update binary as Normal. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Click to expand...
Click to collapse

oscarcx said:
3. #304 in the original thread. I provided a more coherent step by step guide.[/SIZE]
Click to expand...
Click to collapse
When I use KingoRoot it gets stuck at 90%, nevertheless su binary exists and is working.
The folder /data/media/0/Kingo.to.SuperSU however does not exists.
So I skip steps 7-11.
The folders /system/usr/iku and /sdcard/Kingroot do not exists, so I skip 14 & 15 as well
SuperSU does not show "ocupied", but the update binary pop-up (as in step 19) which seems to be successfull (non-recovery install).
I move SuperSU to /system (SuperSU config) and reboot manually.
afterwards the boot is stuck at the "fire" Logo, a soft brick. I tried this two times using adb sideload to reset the system.