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]

Help rooting after following XDA video

I followed the XDA rooting video for my HTC M7 (4.4.2). Nothing showed errors and everything went well until I used a root check app. They reported I wasn't rooted.
I tried weaksauce but it reported I was rooted.
I went ahead and installed xposed framework. Tried to update and it said I wasn't rooted.
I unlocked my bootloader.
I flashed cwm.
I put the su 3.1.2 zip on my phone and went into cwm and installed from the zip file. No errors etc.
Restarted my phone and SU app is there.
But I don't have any root. Tried pressing the build number in phone settings to unlock developer settings - there's nothing mentioning root in there like one site said there would be.
Now I am stuck.... can someone help please?

Try this https://www.dropbox.com/s/awymtnditsptvaj/SuperSU-v1.93.zip
from HTC One

yatindroid said:
Try this https://www.dropbox.com/s/awymtnditsptvaj/SuperSU-v1.93.zip
from HTC One
Click to expand...
Click to collapse
Thank you!!! Worked first time! So it was just the version? I even tried 1.2 last night!

[SOLVED] HTC write system protection?

Edit: Lockscreen.apk and odex deleted with TWRP file manager (mount system before). V4a issue still there, even installing apk through TWRP as flashable zip.
Hi, I was trying to install viper4android on my device. The application is installed successfully, but I can't install drivers. After reboot the app asks me again to install drivers. I also tried to get stock android lockscreen deleting HTC lockscreen.apk. Successfully deleted, but present again after reboot. Should I need s-off to do that? With other models I did this without s-off. Indeed with soft reset, I get the Android stock lockscreen, but with a complete reboot I get the sense one again. Any idea or I just have to wait for a way to s-off?
Sent from my HTC One mini 2 using XDA Free mobile app
Edit: solved

gibihr said:
Edit: Lockscreen.apk and odex deleted with TWRP file manager (mount system before). V4a issue still there, even installing apk through TWRP as flashable zip.
Hi, I was trying to install viper4android on my device. The application is installed successfully, but I can't install drivers. After reboot the app asks me again to install drivers. I also tried to get stock android lockscreen deleting HTC lockscreen.apk. Successfully deleted, but present again after reboot. Should I need s-off to do that? With other models I did this without s-off. Indeed with soft reset, I get the Android stock lockscreen, but with a complete reboot I get the sense one again. Any idea or I just have to wait for a way to s-off?
Sent from my HTC One mini 2 using XDA Free mobile app
Edit: solved
Click to expand...
Click to collapse
Any hint on how did you solved that ? I'd like the original lockscreen aswell

JuJuBoSc said:
Any hint on how did you solved that ? I'd like the original lockscreen aswell
Click to expand...
Click to collapse
You need TWRP recovery
Take backup (you'll never know what can happen)
Boot into recovery > mount > pick system
go back to the main menu, advanced > file manager
You'll find HtcLockScreen.apk and HtcLockScreen.odex in system/priv-app
I deleted them and voilà! No more sense 6 Locksreen, stock android.

gibihr said:
Edit: Lockscreen.apk and odex deleted with TWRP file manager (mount system before). V4a issue still there, even installing apk through TWRP as flashable zip.
Hi, I was trying to install viper4android on my device. The application is installed successfully, but I can't install drivers. After reboot the app asks me again to install drivers. I also tried to get stock android lockscreen deleting HTC lockscreen.apk. Successfully deleted, but present again after reboot. Should I need s-off to do that? With other models I did this without s-off. Indeed with soft reset, I get the Android stock lockscreen, but with a complete reboot I get the sense one again. Any idea or I just have to wait for a way to s-off?
Sent from my HTC One mini 2 using XDA Free mobile app
Edit: solved
Click to expand...
Click to collapse
Are there no flashable drivers for Viper4Android like the rSAP app has?

tomatende2001 said:
Are there no flashable drivers for Viper4Android like the rSAP app has?
Click to expand...
Click to collapse
Yes, but nothing happened, same result...

Are you sure? The rSAP App runs fine after flashing the drivers via TWRP.

tomatende2001 said:
Are you sure? The rSAP App runs fine after flashing the drivers via TWRP.
Click to expand...
Click to collapse
Yes I am.. All the other mods work, except for this...

Where you found the flashable version of the app and drivers?

tomatende2001 said:
Where you found the flashable version of the app and drivers?
Click to expand...
Click to collapse
Link removed - not official version, sorry

But this is not a official version! This zip overwrite your audio configuration! Be carefully. I repaired it with the files from the "big" M8. Runs better than ever.

tomatende2001 said:
But this is not a official version! This zip overwrite your audio configuration! Be carefully. I repaired it with the files from the "big" M8. Runs better than ever.
Click to expand...
Click to collapse
There was somewhere in the official thread in the faq a question like "i can't install it anyway? Then try with the flashable zip", it's the same zip that I posted.. Sorry, I'll give you the right link as soon as I find it... but as you solved it anyway,how did you do it?

After I repaired my phone, I never would like to use this app.

And then installed v4a? As normal app?

No, after this repair I was happy that my phone works again. Until there is no official ROM that I can flash or where I can extract the original files, I do not make any change on my phone again!

Confirmed - it's a problem caused by HTC's system write protection. Liberty Kernel solved the issue with viper4android.

But you need a new kernel. With the Android rSAP App you can create a flashable driver ZIP, I think this is the better way to install drivers for an App. They also create a uninstall ZIP.

tomatende2001 said:
But you need a new kernel. With the Android rSAP App you can create a flashable driver ZIP, I think this is the better way to install drivers for an App. They also create a uninstall ZIP.
Click to expand...
Click to collapse
I couldnt find drivers for v4a, i reflashed stock kernel after installing drivers, the problem was indeed system write, no incompatiblity or stuff like that the app is now installed and finally fully working!

I am happy with the write protection, because you never know, what the "driver installation" changed on your system. In a zip I can take a look about the modification and for example with the rSAP app I KNOW, that I can deinstall all modifications. But I dont know anything about Viper4Android. So I have to look for another DSP manager ...

[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!

Phone stuck on booting screen after install

Hello,
first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8. Yes, i've read now that it doesn't work with the official ROM, but now it's a bit to late.
So. After rooting my S8 today (using TWRP) i wanted to install Xposed. I downloaded an installer from this site because.. umm, i had a brain fart. For some reason my brain took that site as the official website, so i downloaded it from a 3rd Party site instead of the actual website.
I installed the apk and granted root access. After that i clicked on install and Xposed installed successfully. After that it obviously asked me to reboot my device, which i did. But now i am stuck on the Samsung screen of the boot progress. I know i could technically just wipe the phone (again) and start anew, but i'd like to avoid that if possible. I can access TWRP, but if i try to access the system files in the file browser, it shows "0MB" and i can't access them.
I tried downloading an uninstaller linked in this thread, but i don't know which one i should download.
Sorry again for me being so stupid and not reading into it and downloading from some weird 3rd Party site.
Thanks in advance for the help!
EDIT: And yea, of course i didn't create a backup before installing Xposed. So if there is no way to properly uninstall it, i gotta wipe everything once again

Emilia-Chan said:
Hello, first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8.......
Click to expand...
Click to collapse
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
http://dl-xda.xposed.info/framework/uninstaller/
If necessary, you can always try to obtain some additional member guidance and support from the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Sent from my Samsung Galaxy S8 using XDA Labs

Ibuprophen said:
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
Click to expand...
Click to collapse
I tried that before, unfortunately without success. It also may be noteworthy that my brain turned off and downloaded the XPosed installer off some 3rd Party site. I know. Stupid. But it happened.
spawnlives said:
In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Click to expand...
Click to collapse
I waited over an hour for my phone to boot, before and after flashing the uninstaller. I also tried wiping it and even completely formatting the data, everything without any success. It kept on not passing the Samsung screen and eventually bootlooping.
I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now.
Thanks for the advice anyways!

Emilia-Chan said:
.... I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now. Thanks for the advice anyways!
Click to expand...
Click to collapse
You did what I would have probably done myself in this situation by starting from scratch.
I just wanted to let you know that I believe that I had saw somewhere (within the dedicated area of the forum for your device) that individuals were successful with Magisk XPosed.
Though I do understand if you want to stay away from XPosed until your ready again and I'm happy to see that your at least up and running again.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

I got the same even just after the installation of the apk for Systemless Xposed on an Xperia (XposedInstaller_3.1.5-Magisk.apk) found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
I made a reboot as I like to isolate the issues while they happen. That was it: bootloop..