Database Develop

[Q][RECOVERY] Need a recovery, please help!

DROID BIONIC
Android Version: 4.0.4 ICS
System Version: 6.7.246.XT875.Verizon.en.US
So i finally rooted my phone and got superuser. But the method didn't give me a safestrap or bootstrap file to download.
I went online and have dowloaded multiple safestrap apk files (1.0, 2.11, 3.1) and they all said they run on ICS. So i install then and when i go to run them it prompts me and says "unfortunately, safestrap has stopped." and it's followed by another little pop-up that says "Safestrap has been denied superuser permissions." So i can't get into recovery to flash any roms. I'm not sure what to do.
I've tried to wipe the data, caches, and restore my phone, nothing helps. And i made sure my USB debugging is on. But after everything i've tired all my recovery apps still force close and don't get permission. I've also tried to flash my roms using the stock recovery and nothing happens.
I also downloaded titanium back-up and when i go to open the app it notifys me that it doesn't get root permissions, that my phones not rooted. Now with the ICS update theres a Root Check in the stock recovery and it reads “qe 1/1″- so that tells me i"m rooted. So i'm not sure there.
I don't know what to do. Maybe i'm missing a few steps. If anyone could help me out and point me in the right direction, i'd appreciate it.
Thanks in advance!

I got same issue
Did you get it resolved. I spent all afternoon only to be rooted but unable to acess recovery. any elder statesman that have any answers?

No, i haven't fixed the problem yet. Was hoping someone could help me out

This is what happens when i try opening any safestrap app i install.

I would suggest PM Hash code, he created the SS apk, if any one has the answer he would
Sent from my BNTV250A using xda app-developers app

I'm sorry, but who is that? Can you give me a link to his profile please? I'm kinda a noob to this rooting stuff. Hence the problems I'm having lol

Safestrap
Which version of Safestrap did you try? I prefer 3.1 as it has touchscreen capabilities. Do you by chance have bootstrap installed? This could be giving the error.
---------- Post added at 08:26 PM ---------- Previous post was at 08:18 PM ----------
For the safestrap failing to be granted super user access error, you should be able to manually 'whitelist' it in your superuser application. If that does not work, you might want to try a different root program. I tend to use SuperSU, as I enjoy the features, and the realiability.

I tried the versions listed- 1.0, 2.11, 3.1
None of those worked. And no, I've never had bootstap installed. And what's the "whitelist"? I've never messed around with the superuser app, I've only just checked the log and see all my root apps get denied (titanium, safestrap, etc.)
And for the other root method: I'm not sure how to do any other methods, or even find any for that matter. I know my phones rooted, it tells me in my stock recovery.
If anyone could help me out by posting links, that'd help A LOT!

SuperSU
Castronova said:
I tried the versions listed- 1.0, 2.11, 3.1
None of those worked. And no, I've never had bootstap installed. And what's the "whitelist"? I've never messed around with the superuser app, I've only just checked the log and see all my root apps get denied (titanium, safestrap, etc.)
And for the other root method: I'm not sure how to do any other methods, or even find any for that matter. I know my phones rooted, it tells me in my stock recovery.
If anyone could help me out by posting links, that'd help A LOT!
Click to expand...
Click to collapse
Has any application that requires Root Access, or Sudo, ever been granted Super User Permissions? If not, I have a feeling that your root was not preformed correctly. If I may ask, do you remember which "root" method you used? I used HoB Linux Edition, as I run Gentoo. HoB Linux Edition stands for House of Bionic Linux Edition. Here is a link for HoB. (Well, apparently I am unable to post links until i have posted atleast ten times. Message me on Google talk for the link. My GT is later on in this message).
There is a version for Windows, Mac, and the best of all, Os/Distros based off of the Linux kernel (which is based off of the Unix Kernel). As for the whitelist, you are able to go in and select which applications you would like to either always deny, grant, or ask for Super User Access. Again, I've mainly only used SuperSU, as i have had problems with most of the others out there currently. I would not go off of the stock recovery, as, for me at least, when I had an incomplete root, the stock recovery said I was rooted, even though I was not. If you could, could you please post a copy of the log from the super user program that you use? Also, which one do you use, again? If you are online/awake currently, message me on Google talk your questions. i will post anything that solves this issue in the morning. This is do to my mother decided that I need to go to bed. My Google talk is ([email protected]). My Google talk is also best to reach me for quick replies during the hours of: 0700 hours through 1530 hours as I am in my classes at that period of time (High School). Another quick question, did you ever go to Az or Fz Fastboot, during your root process? (Been rooted for over 1.5 years now, a little hard to remember). If not, I doubt that the Root was successful. I am sorry for my late response, as I was watching BSG Blood and Chrome, while shining my shoes for the ROTC inspection tomorrow.
Hope we fix this soon,
~NH85

No, so far since i've rooted this phone superuse has denied every application. I use the superuser v3.1.3.
I was thinking just last night that my root was performed incorrectly, so i went to droidbionicroot website and downloaded a un-root method (as well as several root methods) But i haven't done it yet, I've read that it bricked some users phone's and i don't want that.
I'm on a windows and have tried several root methods. I think the one that actually worked for me was called "PetesMotorolaRootTools_v1.07"
Also, what's Az or Fz fastboot? I'm sorry, I'm still kinda new to this rooting stuff so i appreciate the patience.
I don't have a google talk so I'll just email you at the address. My email is [email protected]

[GUIDE] Root Samsung Galaxy Music S6012 & S6010

There have been many people looking for an easy way to root the Samsung Galaxy Music S6010 (single sim model) and the S6012 (dual sim variant) since this phone came out six months ago. These people have all been frustrated. If anyone found a reliable way to root these phones, they have not posted them here on XDA.
So, here it is, with pics, so that it is easy for the noobiest of noobs.
standard disclaimer: BEFORE STARTING BE AWARE THAT ROOTING VOIDS YOUR WARRANTY (THOUGH YOU CAN EASILY UNROOT AND GET YOUR WARRANTY BACK) . I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE!!!
First of all, thanks to XDA member stat'o'flow who posted the method for Chinese tablets and phones, which seems to be pretty universal, but I am going adapt his method a little to focus on this particular device:
{
"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"
}
HOWEVER IT SHOULD WORK ON MOST DEVICES, INCLUDING CHINESE PHONES AND TABLETS.
Do check if it works on your device and let us know in this thread.
On your PC:
1. Install USB/ADB drivers from Sumsung's website or simply install the Kies software for the Galaxy Music.
2. Install this software: http://www.moborobo.com Management Tools, loads own device specific ADB-drivers
3. Download & install this software from http://www.shuame.com/
- Install on your pc. During Installation uncheck every checkbox except the one that grays out the next-button upon unchecking. Now, there should be three shortcuts on your desktop. we are only going to use the first two.
4. On your device: turn on USB-debugging. Settings>Developer Options>OK>Tick USB debugging
On your PC:
5. Run Moborobo Software, then plug your device to USB-Port, wait until Moborobo has recognized it
6. Run the Shuame software.
7. Wait until shuame app appears on your device's screen. Then on your pc, in the Shuame window click the 4th icon in the top row (step 1). On the screen that appears, click on the 4th icon in the 2nd icon-row (step 2)
8. On the device click the 'Restore my Data' button
9. On the pc, wait for the green line to finish moving to the end (your device might restart in between)
Click the blue button!
On the Phone:
10. Download and install SuperSU app from Play store.
11. Shuame will ask for permission to grant superuser to SuperSU in Japanese, so remember you have to click on the left-hand side button.
12. Download and install root checker app from play store. Check if you are rooted.
13. Uninstall shuame and maroboro using ES explorer or Titanium (you will have to grant these programs superuser permissions first).
14. That is IT!!!
​

You can also use this Shuame software to unroot the device (always remember to do this before giving it in for service or claiming warranty!!!)
And also may other things, as you can see in this pic, with easy to understand translations of the chinese lettering.
You just have to click on 'REMOVE ROOT'

Can u give any method for installing custom recovery guide on this music duos after rooting ??????
I also wanted a good call recording mod
Pls anybody on this forum guide me
thanks
Sent from my GT-N7000 using xda premium
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
Can u give any method for installing custom recovery guide on this music duos after rooting ??????
I also wanted a good call recording mod
Pls anybody on this forum guide me
thanks
Sent from my GT-N7000 using xda premium
Sent from my GT-N7000 using xda premium

Can u give any method for installing custom recovery guide on this music duos after rooting ??????
Click to expand...
Click to collapse
Some developer has to make a custom recovery for this particular model before you can install it on your device. AFAIK there are no ROMS or recoveries available for the Samsung Galaxy Music phones.

Someone asked me this question on PM so I am quoting it here for other people.
Hey bro, do you know what I'm doing wrong? I don't get the recovery option on my phone but it get root... Maybe I'm I deleting the wrong archives on the last part or I just get a temporary root because 30 minutes later it say the us file don't exist
Click to expand...
Click to collapse
I have not encountered this situation before (not getting the 'restore my data' window) but try doing the entire process again. This time install the superSU app before restarting the phone after it gets root. Then delete the kinguser or kingroot app from your /system/app folder with ES Explorer (you have to grant it superuser permission first, and also change permissions for the app).
Uninstall the shuame and moroboro apps the normal way.
Now restart and see if you still got root.
Also please ask questions in the thread instead of pm, so others can also read (or offer) solutions.

FallenAngelmxw said:
Hello! I was looking into your thread about rooting the Galaxy Music, and I just wanted to say that I had the same problem than the other guy that sent you a PM!
I downloaded all the softwares you said, made everything correctly.
And after the sad result, I formatted the phone with Factory Data Reset.
The problem is: I can't make the root, the Android don't asks me if I'll accept the Full Restore, and when it finishes, I go to the root app checker that says my phone isn't rooted.
And even if I make the factory reset the Japanese crazy apps remains there!
And sorry about sending the message through here, I can't post on your thread because the rulles don't let me.
I'm a little desperate about my phone because it came with a lot of apps that eat the entire ram memory, so it starts to be very slow.
I already had tried another root option that didn't solve the problem.
Thanks for reading.
If you discover something about that problem, I'll be very glad!
Click to expand...
Click to collapse
If the phone does not ask you to restore your data, it might mean that there is some anti-virus or other security software that is interfering with the root process.
Or you do not have the correct ADB drivers for the phone. Check that you have the drivers for your model, disable security software temporarily and try again. Use the original USB cable that came with the Galaxy music phone to connect to the PC.
When are you factory-resetting the phone, right after you check with the root checker app or before? Factory reset can remove root. The fact that the Jap apps are still there after you reset means that they have succeeded in installing themselves into the system. Which superuser app are you using, Superuser or SuperSU? SuperSU is better since it also replaces the binaries.

FallenAngelmxw said:
Hello! Thank you for the support!
After resetting the phone I tried to root it again.
It occurs that when you open the root app checker, pops up a message in Japanese (that is the "root" permission), and on you have 2 options, the left one is to allow the access and the right one have a countdown and is the one that deny the access!
When I rooted for the first time, I denied without knowing what was happening.
Now I press the left one that is the allow one, and it works!
I wanna thank you for the thread, and I'm asking you again to quote this and post in the thread, because I don't have a permission.
I always entered in this forum, but never made an account, now that I saw this root a resolved to make one, so that's why I can't post. I have to post at least 10 messages on the general forum to grant my permission in other forums.
Click to expand...
Click to collapse
Thank you for providing this solution. I had also clicked on the wrong button, but somehow forgot to include this in the tutorial! I have now updated the guide.

:laugh:
NEW: UPDATE YOUR SAMSUNG GALAXY MUSIC DUOS S6012 TO OFFICIAL JELLY BEAN 4.1.2!!!
THE COMPLETE GUIDE IS HERE
:victory::victory::victory:
​

Tried the above rooting method but didn't get the RESTORE option so clicked the blue button on the monitor which created an application in Japanese language and the phone shows rooted now.
Only problem is if I disable that new Japanese app the phone says not rooted. so i have kept the app and every app which requires rooting permission takes permission from that Japanese application.
The SuperSU app also works but only for 10-15mins, have to give that admin rights in every 15mins, so i use the japanese app itself to grant permissions. Is this ok what I have done ?

rahulsinha said:
Tried the above rooting method but didn't get the RESTORE option so clicked the blue button on the monitor which created an application in Japanese language and the phone shows rooted now.
Only problem is if I disable that new Japanese app the phone says not rooted. so i have kept the app and every app which requires rooting permission takes permission from that Japanese application.
The SuperSU app also works but only for 10-15mins, have to give that admin rights in every 15mins, so i use the japanese app itself to grant permissions. Is this ok what I have done ?
Click to expand...
Click to collapse
Ya, it's ok. But ideally you should install an English language app such as Superuser or SuperSU. When you install SuperSU, do you also update the binaries? That is required for SuperSU to work. When Shuame asks for supersuser permission for an app, here should be option allow for ever. Once you have SuperSU installed, you can uninstall Shuame with the method described above. The trick is to allow SuperSU superuser permission for ever instead of just 15 mins. The English language apps have this option.
BTW, did you root the ICS build or the new Jelly Bean build?

itsnotmeatall said:
Ya, it's ok. But ideally you should install an English language app such as Superuser or SuperSU. When you install SuperSU, do you also update the binaries? That is required for SuperSU to work. When Shuame asks for supersuser permission for an app, here should be option allow for ever. Once you have SuperSU installed, you can uninstall Shuame with the method described above. The trick is to allow SuperSU superuser permission for ever instead of just 15 mins. The English language apps have this option.
BTW, did you root the ICS build or the new Jelly Bean build?
Click to expand...
Click to collapse
Ya, I did update the binaries, it asks as soon as the app opens but after every 10mins it used to ask me to update binaries. Now what I did is that I made it install as the system app and also checked TRUST SYSTEM USER & now on every app is seeking the permission from Supersu & not Shuame, so i have just disabled not deleted the Shuame permission app.
I had rooted the ICS version not Jelly Bean, quoted the wrong message by mistake.

I have one question, will this root method work with all the phones if you have all the needed USB / ADB Drivers ??

rahulsinha said:
I have one question, will this root method work with all the phones if you have all the needed USB / ADB Drivers ??
Click to expand...
Click to collapse
Ya it should work on most devices.
Only way to know for sure is to try it!

Thanx

itsnotmeatall said:
Ya it should work on most devices.
Only way to know for sure is to try it!
Click to expand...
Click to collapse
There is a great tutorial on "How to root MSI Windpad Enjoy 71" by kibaruk which uses only one English tool Cydia Impactor. I could root my Samsung Music Duos GT-S6012 updated to 4.1.2. JB very easily. No hassle with chinese language. I also faced the problem of not getting "Restore Your data" window while using Shuami software.But with this tool every thing is very smooth.
Vist this page: http://forum.xda-developers.com/showthread.php?p=45409641

mattanur said:
There is a great tutorial on "How to root MSI Windpad Enjoy 71" by kibaruk which uses only one English tool Cydia Impactor. I could root my Samsung Music Duos GT-S6012 updated to 4.1.2. JB very easily. No hassle with chinese language. I also faced the problem of not getting "Restore Your data" window while using Shuami software.But with this tool every thing is very smooth.
Vist this page: http://forum.xda-developers.com/showthread.php?p=45409641
Click to expand...
Click to collapse
Just tested it, it works smooth as butter!! Thanks Mattanur!!
It really is a much easier way to root the Samsung Galaxy Music (Note that I haven't tested with the stock ICS build, only the Jelly Bean 4.1.2 official update)
I will update my 'Update S6012 to Jelly Bean' thread with the method.
Thanks again!!

Not Work
Why not work, i can't see anything on my phone (when i try to install SUPERSU). I've done all you asked. Help

-iCode said:
Why not work, i can't see anything on my phone (when i try to install SUPERSU). I've done all you asked. Help
Click to expand...
Click to collapse
Check with root checker to see if you are rooted

itsnotmeatall said:
Check with root checker to see if you are rooted
Click to expand...
Click to collapse
Oh my god. Home i can reportage the Chinese Root with SuperSU I or Superuser??
Sent from my Kindle Fire HD using Tapatalk

-iCode said:
Oh my god. Home i can reportage the Chinese Root with SuperSU I or Superuser??
Sent from my Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Nothing happens when you try to install either of those apps? There is no popup in Japanese asking for permission? By your rather cryptic (possibly google-translated) reply above I assume you are already rooted?
Try clearing cache of both the japanese apps (in app manager) then try again.

[Q] My HTC One is broken

First of all, my HTC One is unlocked and s-off.
Originally I was using 4.4.2 stock rom, then I started using ARHD 41.0.
It worked very well at first, but when I added a few mods(xposed), I experienced terrible battery drain.
I'm not sure if the mods caused this, or because I just spent a lot more time using my phone.
Anyway, after a while I tried upgrading to the latest ARHD 51.0, but it didn't work, I couldn't boot to android.
So I tried re-installing it(wiped everything), still couldn't boot to android. At this point, I think my phone is actually soft bricked?
I tried to go back and install ARHD 41.0 instead, but it didn't work either. I tried different stock roms and using HTC RUU, all efforts failed.
I remember this recurring error: set_metadata_recursive: some changes failed
My phone is currently running a guru reset rom. I rooted it, but permissions are acting weird.
Most apps or functions which require root access don't work properly.
In other cases, even though I have granted root access to some apps, once I re-open them, request for root access procs again.
Please help!

theplaypig said:
First of all, my HTC One is unlocked and s-off.
Originally I was using 4.4.2 stock rom, then I started using ARHD 41.0.
It worked very well at first, but when I added a few mods(xposed), I experienced terrible battery drain.
I'm not sure if the mods caused this, or because I just spent a lot more time using my phone.
Anyway, after a while I tried upgrading to the latest ARHD 51.0, but it didn't work, I couldn't boot to android.
So I tried re-installing it(wiped everything), still couldn't boot to android. At this point, I think my phone is actually soft bricked?
I tried to go back and install ARHD 41.0 instead, but it didn't work either. I tried different stock roms and using HTC RUU, all efforts failed.
I remember this recurring error: set_metadata_recursive: some changes failed
My phone is currently running a guru reset rom. I rooted it, but permissions are acting weird.
Most apps or functions which require root access don't work properly.
In other cases, even though I have granted root access to some apps, once I re-open them, request for root access procs again.
Please help!
Click to expand...
Click to collapse
post the output of "fastboot getvar all"; remove S/N & IMEI before posting
and please mention which recovery(with version) you are using
you should use TWRP 2.6.3.3 to flash KitKat 4.4 ROMs

theplaypig said:
I remember this recurring error: set_metadata_recursive: some changes failed
Click to expand...
Click to collapse
It's probably a recovery problem, use TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure to check MD5 of the download cause that site does not play nice with download managers

Error: no such tool
Thanks for replying, I didn't realize the issue was so insignificant.
ARHD thread did warn to use TWRP, but I thought it was just OP's preference.
My phone is now successfully running the latest ARHD rom and TWRP recovery.
But as I was setting up my phone, I came across another recurring issue(which started occurring after I messed up my rom in the first place).
When I select reboot in xposed installer, this error message appears: reboot: no such tool
Some threads mention updating busybox and possible errors regarding adb drivers and commands.
Since I have no idea what busybox is, I just downloaded it from play store and installed it. Issue persists.
Any help will be appreciated

theplaypig said:
Thanks for replying, I didn't realize the issue was so insignificant.
ARHD thread did warn to use TWRP, but I thought it was just OP's preference.
My phone is now successfully running the latest ARHD rom and TWRP recovery.
But as I was setting up my phone, I came across another recurring issue(which started occurring after I messed up my rom in the first place).
When I select reboot in xposed installer, this error message appears: reboot: no such tool
Some threads mention updating busybox and possible errors regarding adb drivers and commands.
Since I have no idea what busybox is, I just downloaded it from play store and installed it. Issue persists.
Any help will be appreciated
Click to expand...
Click to collapse
Use "soft reboot"
Sent from my HTC One using Tapatalk

nkk71 said:
Use "soft reboot"
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Soft reboot works, but aren't I supposed to fix it? Kinda OCD can't stand these small bugs, must fix please help!
P.S
This is like the final issue, want to fix it and make a perfect nandroid backup!

theplaypig said:
Soft reboot works, but aren't I supposed to fix it? Kinda OCD can't stand these small bugs, must fix please help!
P.S
This is like the final issue, want to fix it and make a perfect nandroid backup!
Click to expand...
Click to collapse
Perfectly normal, nothing to fix.
{
"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"
}
Sent from my HTC One using Tapatalk

Is it a bug?
nkk71 said:
Perfectly normal, nothing to fix.View attachment 2580435
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
But this function used to work when I was still using ARHD 41.0. If this is normal, is it a bug?

theplaypig said:
But this function used to work when I was still using ARHD 41.0. If this is normal, is it a bug?
Click to expand...
Click to collapse
Don't remember reboot ever working, only soft-reboot. (maybe before it didn't show this error, but it certainly didn't reboot)
Can't really say if it's a bug, maybe it works / is needed on other devices. But for us, soft reboot does exactly what needed.
Sent from my HTC One using Tapatalk

nkk71 said:
Don't remember reboot ever working, only soft-reboot. (maybe before it didn't show this error, but it certainly didn't reboot)
Can't really say if it's a bug, maybe it works / is needed on other devices. But for us, soft reboot does exactly what needed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I remember at one point the error message used to be reboot: not permitted or something similiar.
From what I recall, it worked at first. Then I messed up my rom, it became not permitted. Now it's no such tool.
I guess I'll have to leave it for now, but maybe I should report this issue to the creator of Xposed Installer?
Isn't it weird that such a fundamental function doesn't work on a popular smart phone like HTC One? (Or that no one tried to fix this?)

theplaypig said:
I remember at one point the error message used to be reboot: not permitted or something similiar.
From what I recall, it worked at first. Then I messed up my rom, it became not permitted. Now it's no such tool.
I guess I'll have to leave it for now, but maybe I should report this issue to the creator of Exposed Installer?
Isn't it weird that such a fundamental function doesn't work on a popular smart phone like HTC One? (Or that no one tried to fix this?)
Click to expand...
Click to collapse
Ah, yes that was it: reboot: not permitted
I never really looked into why the reboot option doesn't, as only a soft-reboot is required to get the mods working (and is faster than a full reboot anyway)
Good hunting

nkk71 said:
Ah, yes that was it: reboot: not permitted
I never really looked into why the reboot option doesn't, as only a soft-reboot is required to get the mods working (and is faster than a full reboot anyway)
Good hunting
Click to expand...
Click to collapse
I just remembered when I tried fixing this with adb commands from another thread, cmd shows error: closed.
adb devices works properly, but adb shell has the same error message.

[SOLVED] Safe to continue?? or start again? please help

This is driving me nuts... I was on 5.1.1 and I am trying to get it rooted.
I'm following a guide which goes like this..
1. downgrade to kitkat 4.4 using flashtool
2. root 4.4
3. Install custom recovery
4. Flash 5.1.1 pre-rooted zip
I have had problem after problem and I think something may have screwed up along the way.
I finally managed to get kitkat installed using flashtool and a generic C6903 .108 ftf.
Problem 1... I used 'Easy Root tool' from xda to root kitkat... but it seemed to hang at the cleaning up' stage - is this a problem?
Problem 2... every time I restart my phone - kitkat asks what language etc. Whats that all about?
PROBLEM 3. The guide Im following says to install busybox after rooting kitkat.
I've tried 2 different busybox installers and both of them fail when trying to install bb.
QUESTION: Are these 3 problems linked and will it prevent me from continuing with the guide I am trying to follow??? i.e. do I need busybox to install XZ Dual Recovery and therefore a pre-rooted zip?
Root Checker basic says kitkat is rooted, as does the first busybox installer.
I'm taking a short break from this nightmare, so in the meentime if any of you chaps could advise me on whether or not its ok to continue or if I have fecked up the whole process, that would be great.
Thanks in advance

problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?

I would just start over and try a different root program. busybox is failing to install because the root didn't work.

Gamer4Life said:
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
Click to expand...
Click to collapse
Problem1... thank you, I'll try again
Problem2... Thanks. I thought It could be the lack of a SIM card and then I thought no! that can't be it lol... as usual - I was wrong ha
others... yeah mate, tried 2 different installers from play store - no joy with either.
Thanks for your help

xasbo said:
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Click to expand...
Click to collapse
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate

i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb

thesweeney80 said:
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
Click to expand...
Click to collapse
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.

Gamer4Life said:
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
Click to expand...
Click to collapse
thanks for the tip mate but no joy see my reply to xasbo, cheers

xasbo said:
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Click to expand...
Click to collapse
Thanks mate. I was hoping Gamer4life might be right as there was no Supersu installed.
I installed supersu from play store no problem... but when I try to update binaries it says' update failed. Please reboot and try again.'. tried reboot but same story.
I guess I'll try 'easy root tool' again and then will give kingroot a bash if needbe.
One last pre-emptive question...
If I root kitkat using kingroot... should I replace kinguser with supersu before proceeding with XZDR and a pre-rooted zip or will kinguser be sufficient to continue.
Many thanks to you and everyone else who has tried to help me with this clusterf*ck,.. I appreciate it

can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)

Gamer4Life said:
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
must have been a glitch in the matrix mate becuase its now working (Possibly thanks to your suggestion of installing Supersu?).
I reconnected to PC in order to give 'easy root tool' another crack at it.
As soon as I start install.bat It says checking if device is rooted AND I get a superuser request on my phone for adb.shell - Happy days!
I granted root access to adb shell and the root tool says Job Done. Root success etc.
So I disconnect and try to update su binaries and it worked first go!!!
*Touch wood* I think I'm now past the tricky part and it should be plain sailing from here on in. lol
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:

Gamer4Life said:
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
Correct, TowelRoot doesn't work for this version.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
thesweeney80 said:
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Click to expand...
Click to collapse
:good: godspeed

@thesweeney80 you are welcome have fun

xasbo said:
:good: godspeed
Click to expand...
Click to collapse
Gamer4Life said:
@thesweeney80 you are welcome have fun
Click to expand...
Click to collapse
you fellas are the muts nuts.
All done, everything went smoothly once I got kitkat rooted properly.
MANY thanks for all your help.
Honestly I wouldnt even bother owning a smartphone if it wasnt for the peeps on XDA... F*cking awesome. THANKS :good: :highfive:

:good: awesome! don't forget to pay it forward sometime.

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.