Database Develop

Root - Superuser crashes / gets terminated

Hello community,
I was a reader of the site for long time. So I decided to register here, because I have some troubles with my new rooted Xperia Z.
Unfortunately all apps with root permissions are working a bit strange. Root Checker and Root Explorer are working after several crashes of Superuser. By opening these apps, I always get a message prompt, that Superuser has been terminated.
SuperSU doesn't work and quits while trying to install the in-app update.
I also changed the owner and the chmod permissions for these apps, but nothing changed at all.
It seems to me, that something went wrong during the root procedure. I completely followed the guide written by DooMLoRD(http://forum.xda-developers.com/showthread.php?t=2186368). The only different part was, that the service menu opened automatically. After that, I fixed the NFC issue. Hopefully, I don't have to reset the device.
Firmware build: 10.1.A.1.434
Do you have any suggestions for me?
Thanks a lot!

Fabowski said:
Hello community,
I was a reader of the site for long time. So I decided to register here, because I have some troubles with my new rooted Xperia Z.
Unfortunately all apps with root permissions are working a bit strange. Root Checker and Root Explorer are working after several crashes of Superuser. By opening these apps, I always get a message prompt, that Superuser has been terminated.
SuperSU doesn't work and quits while trying to install the in-app update.
I also changed the owner and the chmod permissions for these apps, but nothing changed at all.
It seems to me, that something went wrong during the root procedure. I completely followed the guide written by DooMLoRD(http://forum.xda-developers.com/showthread.php?t=2186368). The only different part was, that the service menu opened automatically. After that, I fixed the NFC issue. Hopefully, I don't have to reset the device.
Firmware build: 10.1.A.1.434
Do you have any suggestions for me?
Thanks a lot!
Click to expand...
Click to collapse
Try re-rooting the device

I already did a second try. Nothing changed, I've only got the message, that superuser app has been already installed.
Or do you mean, I have to reset the device and re-reoot it?
Any more suggestions here?

Sorry guys, I'm not a fan of bumping this topic, but before I try it with a factory reset, does anybody has a suggestion on this problem?

[Q] Bootloader unlocked, SuperSU installed, can't write to system?

Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?

neil.io said:
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
Click to expand...
Click to collapse
You flashed the latest version of TWRP custom recovery?

samwathegreat said:
You flashed the latest version of TWRP custom recovery?
Click to expand...
Click to collapse
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img

neil.io said:
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
Click to expand...
Click to collapse
That might be the issue. It might not be compatible with 4.4.3
Try this one: http://techerrata.com/browse/twrp2/ghost
Also, which version of SuperSU are you using? There was a new one released recently. Find it here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip (Flash it from within TWRP - install ZIP)
Please update, and then advise whether or not your issue is resolved.
EDIT: Also, make sure you are using the "stericson" busybox variant. Others have been reported to cause issues.

Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!

neil.io said:
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
Click to expand...
Click to collapse
Open SuperSU, and check to see if busybox is listed under apps. There should be a green "#" symbol next to it. It SHOULD have prompted you to grant access to it, so perhaps at some point you either denied the su request, or didn't see it. If you see a RED "#" symbol, tap it, and change to "Grant".
Please advise...

It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.

neil.io said:
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
Click to expand...
Click to collapse
I would suggest a full return to stock (follow the return to stock thread in the general sub-forum). This is not normal....
You appear to be using the XT1053, correct? Take caution to NOT downgrade or you could end up with a brick.
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.

samwathegreat said:
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
Click to expand...
Click to collapse
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.

neil.io said:
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
Click to expand...
Click to collapse
How did you SBF to stock? Did you use RSD Lite? Did you retain userdata, or wipe everything (suggested)?
The stericson variant installs fine for me...granted I'm on 4.4.2 (the latest for my variant).
I did NOT use smart install...just used regular install to /system/xbin (You might consider trying smart install if you haven't yet...)
Honestly, I'm out of ideas. Although the "stericson" variant is recommended, perhaps you should try another version from the market if you need busybox.
I've done extensive searches and haven't found anyone else having a similar issue - even with Moto X on 4.4.3

I gave up and used the recovery method. Really odd - it does seem like the other installer apps couldn't mount /system as writeable, but it's weird that other apps that installed to that area worked.
Anyway, thanks again!

[Q] Super su binary update making sdcard & system read only XPERIA M2 DUAL 4.4.4

I downgraded my Xperia M2 dual d2302 to 4.3 and rooted with towelroot and then flash 4.4.4 followed by flashtool force towelroot using super su. This would uninstall super su on my phone and install its own super su binaries and busybox content. The super su pro would however, remain installed. So, I would have to redownload the super su and as soon as i would open it, it would ask for binary update and then ask for reboot. I would just follow the prompt without question. As soon as it reboots,though the root would be there but sd card and system rewriteable will be gone and there is no way to make my system rewriteable without flashtool reflashing back to 4.3 and following the long procedure. I till now, would blame kitkat and sony for that. This continued for over 8 days till I realised that the real culprit was not sony or kitkat but super su binary update followed by reboot. This is highly anoying. What is the point of root if system or sd card writing is not allowed? For now, I am living with super su by canceling the binary update everytime I open it. I have OCD and I find it highly annoying. I tried searching for an option to cancel auto search for updates bur in vain. My phone works just fine without update. I need no updates and need a way to stop super su asking for update everytime. Please suggest me something.
I have now discovered that even if I cancel binary updates, supersu auto updates causing the same problem. So, now I have decided to live without Supersu as supersu is not needed for root. I have an unlimited root access for all my apps which have root permission now and to add icing to the cake, my bootloader is locked. If anyone else is searching for a way to make Sony Xperia M2 dual 4.4.4 system writebale without unlocking bootloader, just follow:
LOCKED BOOTLOADER
1. Downgrade to JB, Root your Phone using Towel Root in Jelly Bean
2. Update via OTA to KK 4.4.2 or KK 4.4.4 whatever you need (4.4.4 is recommended)
3. In this process, don't try to install or uninstall anything
4. Wait for booting finish
5. Install latest SuperSU from Play Store
6. Open Flashtool in PC
7. Connect your phone to PC
8. Now flashtool will describe your phone information, then click Root Tab in top, after that choose force root by TowelRoot
And after this, do not install supersu or any other root control app. Just let your phone be as such without updating binaries or anything and you will have root. You will have unrestricted root on Xperia M2 dual, Enjoy and remember not to install supersu, kingsu, cm superuser or any similar app.

I was thinking to help you, but then i was worried if something else goes wrong, then you will blame me, just like you blame super su.

Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt

gauthamraob said:
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
Click to expand...
Click to collapse
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
---------- Post added at 02:42 PM ---------- Previous post was at 02:31 PM ----------
BTW, tell us what do you need on your device that will make you feel better. (About the superuser @ root thing of course)

NeoLogY said:
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
Click to expand...
Click to collapse
No, I am already having root . I have integrated most of the updates to my system app to my sys/app folder through lucky patcher and have installed the modded play store . I can even edit and delete system files in "ES explorer" file manager and stop items from startup using "all-in-one-toolbox" boot manager. I have an older version of su binaries which was installed automatically into my phone by "flashtool by androxide" using the force root mode using towel root :good: . But the supersu app was not installed and if the app existed before rooting, flashtool would uninstall it and also replace the new su binaries with an older version ! So, I already have full root access without the supersu app.
As far as i know, supersu is not needed for root. It is only a gatekeeper app which restricts the unlimited access of root to any app by making the apps that need root to ask for permission first. Without supersu installed, root apps get root access without asking permission provided binaries (any version) are already present. Also, for normal people who don't know or can't install binaries directly, they rely on apps like supersu, CM etc for installing the binaries. But once the binaries are installed, the supersu app is no longer needed for root (except in cases of OTA updates or updation of binary to a newer version) but instead works as a security guard for root.
Edit:
What I want is a way to make supersu submissive and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like.

What I want is a way to make supersu submissive to my command and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like and must not be done

Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?

NeoLogY said:
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
Click to expand...
Click to collapse
At present I am using my phone without supersu as I will have to spend a lot of time downgrading to 4.3 and then rooting followed by painfully slow 4 OTAs in succession (there is no single direct OTA from 4.3 to 4.4.4 on Xperia M2 dual, unfortunately :crying: ) followed by installation of all my apps. I too wish there was a fix for supersu but the time I'll have to spend on that will be enormous and also considering that in this september my phone will mostly get lollipop 5.1, the 4.4.4 woes will soon be history.
Also, I want to mention that I haven't unlocked my bootloader yet. If I unlock my bootloader, all these problems with supersu will vanish. The actual difficulty I am facing is because there is no single post on the internet that says how to get system to be rewriteable without unlocking bootloader in Xperia M2 devices. Every post I have read of only has people with unlocked bootloader saying what to do and people with locked bootloader complaining that they aren't able to make their system rewriteable. I am probably one of those rare people who managed to get complete root with locked bootloader and hence facing the issue of lack of peer help.
Anyways, I really appreciate your interest shown in helping me. If I ever have to update my binaries in the future I will definitely take a log of it and pm it to you in case similar situation arises.
Cheers.

Same thanks to you. Actually, i think it is better to put the log here, as more hands and mind will be able to reach it, meaning higher percentage on discovering any hidden in the log. You are right about the lock bootloader, even until now i still unable to manage to truely understand about bootloader, as i didn't have any device with it to get inhand with the system. As always, i do appreciate any kinda knowledge exchange. Thanks in any way.

That's exactly why your system is read only and you can't move apps/data to sd ect without supersu installed and the binaries updated and Sony ric killed you don't have full root r/w access to system. The way you have rooted your device is the same way I did mine it's the easiest way there is if you can't get it right doing that way then maybe you should put your Phone back to stock. Flash jb, root with towelroot apk(at this point do not update anything), now update over the air to 4.4.2 then again to 4.4.4(again update nothing but phone)root will stick after each update. Download supersu connect your phone to flashtool and click on the force root tab(kills Sony ric installs supersu binaries and busybox) making system r/w
Search on here for the m2 forum if you still have problems
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.

Systemless SuperSU has big problem on MIUI 8 ROM

Hello,
I'm using MIUI 8 on my phone, its based on marshmallow 6.0.1. I rooted my device using supersu stable 2.78 as systemless mode. The problem is all need-root apps take long time to call supersu at first time it launched. Sometimes need-root app crash if it does not get superuser access for long time. The culprit is on systemless supersu, Superuser.apk installed inside /data partition instead of /system so it won't load on system start. Although i already add SuperSU in startup list, but it was not much help. I did not get this issue on CM13 based rom. Temporary solution is I need to open SuperSU first before open need-root apps for first time.
How to get rid from this issue?
Cc: @Chainfire

Have you found solution yet. Me too facing similar problem, some of my personal apps crashing, I found a system based super Su zip let me flash and report back..

herecomesmaggi said:
Have you found solution yet. Me too facing similar problem, some of my personal apps crashing, I found a system based super Su zip let me flash and report back..
Click to expand...
Click to collapse
Yes. Use phh superuser + magisk latest version. :good:

actually this is not the right answer, wrong thread
Hi
I'm sorry for bumping old thread, I've same issue with very same ROM, MIUI 8 8.1.6 run on mi4W device, magisk 13.3
how I managed to solve this is somewhat ridiculously simple yet make me wandering over the internet for about 4 hours in 2AM,
I forgot to activate the "install from unknown source". after that everything run like magic.
FYI: I've done everything via adb shell via TWRP before the "what if" idea come to my head
Click to expand...
Click to collapse

Amazon Fire 7 (CM 12.1-20160710-UNOFFICIAL-ford) -- Lost Root and SuperSU Binary Busy

Today I was having Chromecast issues with Netflix, so I factory reset my Chromecast and then had some issues getting it set back up. I had to point the Fire 7's WIFI towards the Chromecast because it couldn't find it otherwise.
After this strange series of events, I rebooted and decided maybe I would remove Netflix and install the last good version I used. I opened Titanium Backup and was told that it could not acquire root. Then a notification for SuperSU popped-up saying "The SU binary needs to be updated!". When I click on it, SuperSU opens and says "SU Binary occupied". When I click "how to solve", I'm taken to a blank WIKI page.
I rebooted. Turned on "Root access" (for apps) in "Developer options". I then rebooted again. I am still unable to achieve Root access!
My tablet was originally running Fire OS v5.1.3 and I downgraded it to v5.1.2. I Rooted v5.1.2 using Root Junkie's tools and then installed CM 12.1 using the guide from the developer's thread.
Firstly, why did this happen or how did this happen?
Secondly, what can I do to gain Root again?

Blastyrant said:
Today I was having Chromecast issues with Netflix, so I factory reset my Chromecast and then had some issues getting it set back up. I had to point the Fire 7's WIFI towards the Chromecast because it couldn't find it otherwise.
After this strange series of events, I rebooted and decided maybe I would remove Netflix and install the last good version I used. I opened Titanium Backup and was told that it could not acquire root. Then a notification for SuperSU popped-up saying "The SU binary needs to be updated!". When I click on it, SuperSU opens and says "SU Binary occupied". When I click "how to solve", I'm taken to a blank WIKI page.
I rebooted. Turned on "Root access" (for apps) in "Developer options". I then rebooted again. I am still unable to achieve Root access!
My tablet was originally running Fire OS v5.1.3 and I downgraded it to v5.1.2. I Rooted v5.1.2 using Root Junkie's tools and then installed CM 12.1 using the guide from the developer's thread.
Firstly, why did this happen or how did this happen?
Secondly, what can I do to gain Root again?
Click to expand...
Click to collapse
Lol. Unlock bootloader and flash latest lineage:
UNLOCK: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
LINEAGE: https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-12-1-t3639447

Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?

From the error message I am guessing that you are on SuperSU 2.82. I would try uninstalling the SuperSU apk (just the apk, don't unroot) and install version 2.79 of the apk. Sometimes I have seen that error message (on 2.82) when the su binary has somehow been deleted. It tries to replace the binary but fails. If 'daemonsu' is still present in xbin it may be possible for SuperSU to fix the installation but this works better on 2.79 than it does on 2.82.

Blastyrant said:
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
Click to expand...
Click to collapse
If you have lost root your only practical options are: 1) restore FireOS and start from scratch; or 2) follow the links suggested by @Rortiz2 (here).

MontysEvilTwin said:
From the error message I am guessing that you are on SuperSU 2.82. I would try uninstalling the SuperSU apk (just the apk, don't unroot) and install version 2.79 of the apk. Sometimes I have seen that error message (on 2.82) when the su binary has somehow been deleted. It tries to replace the binary but fails. If 'daemonsu' is still present in xbin it may be possible for SuperSU to fix the installation but this works better on 2.79 than it does on 2.82.
Click to expand...
Click to collapse
Hello thank you. I like this idea, it will be pretty easy give it a try! Is there a safe source for old SuperSU .apks that you can recommend to me?

Blastyrant said:
Hello thank you. I like this idea, it will be pretty easy give it a try! Is there a safe source for old SuperSU .apks that you can recommend to me?
Click to expand...
Click to collapse
The best place is Chainfire's blog. A link to the page with 2.79 SR3 (bug fix update) is here: https://chainfire.eu/articles/970/SuperSU_v2.79_SR3
Download the zip file: the superuser apk is in the 'common' folder. Click on the apk file from a file browser to install. You will have to enable the option to 'install apps from unknown sources' but you will be prompted to do this if you have not already done so.

Blastyrant said:
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
Click to expand...
Click to collapse
No need to install linux. Just use VirtualBox or bootable USB!

Rortiz2 said:
No need to install linux. Just use VirtualBox or bootable USB!
Click to expand...
Click to collapse
Hi. Thank you for those suggestions. I Googled quickly but am still afraid using both options is not something I'll be able to dive right into. I'm also a little confused that the guide for unlocking the bootloader mentions "Install python3, PySerial, adb and fastboot." I'm unsure how to do this for a virtual install or a bootable USB. My Linux usage dates back to a 1 month course in the mid 2000's. =P
Am I making this out to be more difficult than it actually will be?

MontysEvilTwin said:
The best place is Chainfire's blog. A link to the page with 2.79 SR3 (bug fix update) is here: https://chainfire.eu/articles/970/SuperSU_v2.79_SR3
Download the zip file: the superuser apk is in the 'common' folder. Click on the apk file from a file browser to install. You will have to enable the option to 'install apps from unknown sources' but you will be prompted to do this if you have not already done so.
Click to expand...
Click to collapse
Thank you! I bookmarked it and grabbed the file. I've just reinstalled it and am being told "no root detected". =(
Still, it was worth a try!

Blastyrant said:
Hi. Thank you for those suggestions. I Googled quickly but am still afraid using both options is not something I'll be able to dive right into. I'm also a little confused that the guide for unlocking the bootloader mentions "Install python3, PySerial, adb and fastboot." I'm unsure how to do this for a virtual install or a bootable USB. My Linux usage dates back to a 1 month course in the mid 2000's. =P
Am I making this out to be more difficult than it actually will be?
Click to expand...
Click to collapse
Yes. It's very easy. The difficult part is short the pins but since you have 5th gen you don't need to do that.
Enviado desde mi Mi A2 mediante Tapatalk

Rortiz2 said:
Yes. It's very easy. The difficult part is short the pins but since you have 5th gen you don't need to do that.
Click to expand...
Click to collapse
That said, you have to decide if the benefit is worth the effort/hassle. In the US $64 scores a very serviceable 8" tablet at Walmart running the latest version of Android that runs circles around all Amazon offerings except the HD10.