Database Develop

[Q] HTC One Xposer Trouble

Hey guys, just a heads up, I've been a anon on this site for a while, but had to sign up after getting some trouble to post.....
Anyways, just got a fresh root on my HTC One. And before someone asks if its fully rooted or not, yes it is. No partials here. I saved a backup just incase using twrp and have it unless I get further problem.......To the real issue.....I installed the Xposed Installer 2.6.1 apk from the link, and after installing, and opening, it says that it isn't up to date in red text and needs the framework. I attempted to update it through the app, SuperSU asks access to be granted and it reboots. I know I am supposed to hit a screen where the update, and framework is installed, but nada. After everything is back on, Xposed Installer shows the same red text as before. I have restored the backup, re-done the root, and even tried installing 2.6 and 2.5.1 They all throw up the same thing. The framework isn't installed and upon attempting, it asks for access, then promptly reboots. Any help at all would be appreciated! Thanks ahead of time!

Sounds like HTC has protected the /system partition and reboots whenever an app tries to write to it. You could try selecting a different installation mode (via recovery) and see if that works better.

Installing SuperSU causes black screen

I just updated my phone from 6.0 to 6.1. I had it rooted before with SU and TWRP installed. After installing 6.0.1 it works great. I then installed the latest TWRP as well, and that worked fine. However once I install the latest SU binary and attempt to boot into the phone, I get nothing but a black screen.
I can boot back into the bootloader with the power button + volume down to flash system, and then the phone will boot again. But as soon as I put SU back on there, I see nothing but the black screen. Also, after updating to 6.0.1 I started getting the "This device can't be trusted" screen when turning on the phone. It still boots after that, but it wasn't happening before.
Any ideas besides wiping and starting from scratch?

Is that SuperSU 2.62? Just asking because you haven't said. I haven't bothered rooting my N6 this time, since my only real need was a firewall and Netguard does the job perfectly, but I understand from general reading that Marshmallow is choosy about the SuperSU version.

SM-G800F rooted stuck in bootscreen (got TWRP access)

I wanted to try and hopefully learn little about rooting. Have been reading forumposts and tutorials for hours before I started.
Then I got this problem that I have been trying to solve for hours. But my conclusion is I need help solving it.
Tested on this phone that just were collecting dust.
Samsung Galaxy S5 Mini (SM-G800F) and I think it was running 4.4.2. (this is all I remember off the top of my head)
Problem / What happend (long version):
Rooted phone. Downloaded SuperSU and Flashify and installed TWRP 3.0.0 (http://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-twrp-3-0-0-t3313775). I had no SD-card so I skipped doing a backup. Everything worked fine (for a normal user). Downladed a Root Uninstaller app also Debloater-setup-v3.90.exe (http://forum.xda-developers.com/devdb/project/dl/?id=12623). Did not freeze or uninstall anything before checking in this forum that it was OK. But after a while I could not access my homescreen it just turned up blank but I could still use other functions/apps. Rebooted the phone in order to get it to work but got stuck at the bootscreen. Tried to fix it via TWRP but the program freezes after a while or just reboots the phone back into Samsung bootscreen.
Problem / What happend (short version):
Rooted - got Flashify and SuperSU
TWRP 3.0.0 installed (no backup made)
Debloater-setup-v3.90.exe and some Root Uninstaller app used (searched on this forum before doing any changes)
Homescreen just blank, other functions/apps worked
Rebooted the phone and got stuck at Samsung bootscreen
TWRP access but the program freezes/reboot after short time
I did try "Factory reset". But the screen froze and the phone slowly started to heat up.
Later on I searched about it and it might have something to do with KNOX?
Any solution is fine since I don't have anything thats need to be saved. I can try any working stock/custom ROM (just not sure how to get it into the phone, yet).
Yes I am a novice so the simplest thing might even work.

Have you tried to flash stock ROM for your device using Odin? If it fails you may want to check this:
http://forum.xda-developers.com/galaxy-s5-mini/help/g800f-failed-odin-firmware-upgrade-fail-t3131782
If it doesn't fix your phone you may have a hardware problem.

Rooting Samsung Galaxy Tablet E (8.0) SM-T377V Please Help

So I've had success rooting the SM-T377V thanks to electronhacker post on the forums.
I thought I would give my experience because anyone else doing this will most likely run into the same problems I did. I still have a few problems I am running into. I hope someone can help me out.
electronhacker had said to downgrade to stock firmware LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop, from firmware MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow using Odin.
I ran into problems finding LMY47X.T377VVRU1AOL7 but I eventually did find it on samsung-firmware.org Thank you moonsh0t!
It did actually work and passed with Odin, however it got stuck in a bootloop. I thought there was nothing that could be done but after looking into the bootloop matter more I figured out how to get out of it and start it up.
1.) Wait for the device to turn off while it's bootlooping.
2.) Then hold down the power button and the volume up buttons to enter recovery mode.
3.) Restore factory defaults. "I think this actually gave me an error but clearing the cache got it to work."
4.) Clear the cache.
5.) Reboot the device.
There you have it now you're out of your bootloop, the device will start up now.
Now that we have downgraded electronhacker had said to run a program called Kingoroot using the Windows application.
I ran Kingoroot and it got stuck at 44% and my screen went black and would not come on or turn off. I am pretty sure you call this a soft brick, but maybe it's called hard brick as there was nothing that could be done.
So this is what I did to Unbrick the tablet:
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
I tried to use Kingoroot again. This time it got stuck at 51% and my screen on the tablet got stuck. Nothing was responding, not the power buttons, the volume buttons, home button, nor the screen. This is because Google Application had showed up on the tablet while I was in the middle of rooting. The Google Application said "Do you want to enable Google Security?".
Again;
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
The device booted normally and I tried Kingoroot again. I wasn't going to give up. This time it worked, 100% Root Successful. I couldn't believe it the SM-T377V was rooted. I checked and verified with Root Checker.
Now this is where I need help!
#1.) The device only stays rooted until you restart it. Then you have to Re-Root it with Kingoroot every time you restart. I found out if you run SuperSu and go into setting you can stop this from happening. I'm not exactly sure what you do yet because I can NOT get into SuperSu. It tried to install the binaries but gets interrupted by Knox. It says disable Knox on SuperSu but this does NOT work. This tablet does NOT have a way to open Knox in order to disable it. So I need to figure out how to delete it that way I can run SuperSu and stop the never ending root process. So if someone could help me figure out how to do that I would very much appreciate it.
So far I've figured out that you can run an application called Titanium Backup to freeze the Knox files and then remove them followed by a Re-Boot to get rid of Knox. I looked further into my SuperSu problems and found out that you can manually download a SuperSu.apk file that should bypass Knox and actually disable it.
Here is my new problem, installed Titanium Backup from Google Play Store only to find out that I can't freeze the Knox settings unless I pay the $5.99 for Titanium Backup Pro. So I removed Titanium Backup and downloaded Titanium Backup Pro.apk which I found for free on the internet. I can NOT install it though, because I have a new error that says "APP not installed".
This happens with the SuperSu.apk that I found on the internet too. I've tried a lot of things but can't get them to install. Google Play Store gives me error (-504) I've tried clearing cache and data for Google Play Store and Google Play Services but no luck. I even tried downloading APK Installer but it doesn't even work. Please help I don't know what to do.
02-09-2017
<UPDATE>
I'm at a loss, so I decided to do a factory reset from settings and that did not get the applications to install. So then I tried to clear the cache but again no suck luck. Then I decided to enter recovery mode and factory reset, but then got stuck on "Your tablet is getting ready for you". or something along the lines of that and wouldn't get past that on start up. (This is because I disabled setup with another application, and is my fault.) Not being able to get past that I realized I had no choice but to Re-Flash the System Update LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin and that was successful, thank God. Now I have to Re-Root and before installing the wrong applications, which are Google Play Store SuperSu and Titanium Backup. Reason being that once you install these once and uninstall them you can't install them again without getting error (-504) in Google Play Store or even outside the Google Play Store such as manually downloaded .APK files or you will get the error "APP not installed".
Here is my idea, and I haven't done it yet. Re-Flash, Re-Root, Install for the FIRST time the right SuperSu.apk and Titanium Backup Pro.apk in order to disable Knox and stop the never ending Re-Root every time the tablet it restarted.
02-10-2017
<UPDATE>
I have been running Kingoroot with my PC using USB. This gives me temporary Root access until Re-Boot. So I installed Kingoroot.apk and tried using to mobile application but this one works, but I get stuck in bootloop on restart of tablet. Then have to Re-Flash with Odin to get out of bootloop. I'm not having any luck.
#2.) Even with my temporary root I can not seem to install Xposed because of SDK 22 not supported. I was wondering if anyone knows a way to get it to work on SDK 22 so I can run IMEI Changer. Unless there is another way to change the IMEI without Xposed.
Thank you to electronhacker for your post I found on this forum which has made me a lot of progress, and thank you moonsh0t for your help redirecting me to find that firmware. :good:

I just got a SM-T377V this weekend and have been trying o root it as well. Wow seems like nobody has had any luck getting a reliable root on it. Please update me as you keep at it! Brent your attempts at this are amazing!! Keep at it!

I'm trying to get this thing rooted too, so please keep me updated if you find a
Way!! Thanks for your help!

Yep
Ok

Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.

Alright, so your goal is to run an IMEI changer, but why?
Also my luck was to get it temped root and try and use chainfire's supersu to take over.
from there I tried unlocking the bootloader with samdunk. The issue though, is the CID was deleted from the tablet, so when I restarted, never ending bootloops.
I just Odin'd it back to the AOL firmware today, will look more into samdunk later.

Treyday645 said:
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Click to expand...
Click to collapse
If you use Odin to flash android 5.1.1 via package T377VVRU1AOL7, you can use the kingroot or kingoroot app (desktop or android) to temporarily root the device. From there, if you delete the kingroot or kingoroot app from the device you can use SuperSu to take the binary over. From there you can use any flashing apps you'd like.
The issue is at this point, the second the device turns off, when it comes back it will no longer have root. (note so far in my attempts I've found that Kingroot, will reboot rootless, whereas kingoroot will bootloop.)
Kingoroot will bootloop because it modifies the boot file in some way, which causes the bootlooping. The work around to this is just flashing over the previous android. However, if you flash with Odin, you lose root, but keep your files.
Going back to flashing, when you attempt to use Odin to flash other packages, they are denied, due to the locked bootloader, however, you can use Flashfire to flash these firmwares. I attempted to flash the T-377P firmware and bootloader. Obviously the locked bootloader stayed locked, the recovery partition got errored out, but the android system itself actually started. Just sans root.
It's worth noting I've also attempted using SamDunk, the S5 bootloader unlocking tool, and so far all I've noticed is it deletes the CID file and doesn't finish. So I'm of the impression that the temp root, isn't a full root either.

I can't flash my device.

Installing TWRP was one of the first things I did when I got this Lenovo phone.
It worked like a charm, I pressed the Volume Keys and the Power button simultaneously and voila! TWRP opened. I was planning to install a custom ROM, so I decided to backup my device, just in case something goes completely wrong. I backed it up, then tried to move the backup from the /data partition. That went kinda wrong and for some weird reason TWRP didn't do anything but show this loading bar on the bottom of my screen.
Since TWRP was being unresponsive, I decided to remove the battery from my phone.
When I tried to access TWRP again, to my surprise, it was gone. The stock recovery appeared instead. I tried reflashing TWRP using both SFP and ADB/Fastboot, and even though the transfer was successful, the Lenovo recovery was still there. I booted to Android and saw that the "OEM Unlocking" option was disabled, even though I had enabled it. I re-enabled it, tried all the things I mentioned before and I got the same result. I opened up Android and.. OEM Unlocking got disabled.. Again.
I enabled it, yet again, tried going to fastboot, where I tried unlocking the bootloader. FAILED! I also tried side loading SuperSU.zip. FAILED!
As a last resort, I used Kingoroot to root my device, and to my surprise it worked.
I still can't seem to be able to flash CWM/TWRP, though, and I would like to install Xposed. SuperSU is also a necessity for me.
TL;DR I can't flash a custom recovery even though I could, Kingoroot worked for me, I need to get SupeSU, Xposed and a custom recovery. Side loading/Flashing using ADB isn't working, OEM unlocking gets disabled every time I reboot my device.

Now that you are rooted, i would suggest you to try 'flashify' and check if you can get your twrp working again. I still doubt it would, since you said you werent able to get it installed through fastboot before, but first give it a try.
When you confirm it working just flash the supersu zip using whichever method you like.