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.
Related
Hello,
I am hoping somebody can give me a little advice on my issue.
I updated to the OTA 2.2 via the full SBF file, i then rooted using the one click root. I then installed the 928 black glass theme that deodex's at the same time.
Everything was running fine. I them wanted to change some of the icons by modifying the framework file. I booted into recovery and created a back up before attempting to change the framework file. I them made the changes to the icons i wanted to in the framework file. a sent it back to the phone via ADB. However the phone was stuck in a boot loop. I then pulled the battery and it rebooted into recovery. I selected my backup and it started to load. The problem is it gets to where it says "Restoring Data" and it just hangs there. I let it sit at that point for over 20 min with no change. I also have tried to go into the advance recovery and just restore the data file on its own, but it also freezes.
Anyone know what might be the issue here?
Thanks
Hello!
I have tried installing the framework, but it will not start. Here is how it went:
First, I have installed rooted 4.4.2 firmware on my HTC Desire 601. I have tried installing Xposed, but it turned out that the modified app_process gets wiped after reboot. So, I have just copied it in a different spot and put it in place using Aroma FM, and it stayed there.
So now, as you can see on the first screenshot, I have both files installed and in place.
However, as the second screenshot shows, the framework is not active.
I am using the latest stable release from the official site.
What shall I do to start the framework?
EDIT: I have also tried the flashing method, but it halts on "Exposed apk must be installed first!" despite the fact the I have it installed already.
Do you see any kind of error in the log section? If yes, please post that log, there are some share options in the menu. Otherwise, please get a logcat immediately after restarting the phone, which hopefully contains the startup sequence.
rovo89 said:
Do you see any kind of error in the log section? If yes, please post that log, there are some share options in the menu. Otherwise, please get a logcat immediately after restarting the phone, which hopefully contains the startup sequence.
Click to expand...
Click to collapse
The error log is empty.
What's more important is that now, upon startup, I have about 30 seconds to hit "install" and "soft boot" in the installer, or else the phone reboots; if I pull that off, the framework works flawlessly.
Now, my only problem is the SuperSU nagging me to update, even when I flash the zip. I'll try just putting it in system using AromaFM.
Im sure ill get flamed but i have searched and couldnt find an answer.
I have a z2 odexed stock with root. Just updated new firmware via pc companion to 17.1.2.a.0.314.
i downloaded the xposed installer and that went well. Then downloaded the serajrs xposed module so i can get different themes to work, extended power menu etc. everything seemed to install fine however now after rebooting i get this error.
it boots up but stays on the home screen and i can do is keep hitting ok to acknowledge the problem but i cant do anything else.
It was the stock rom so i dont have any custom recovery to go into to restore a nandroid or flash another rom (which i didnt want to do).
All i have is my titanium backup but i cant get past the error, any help would be greatly appreciated
* the error appeared about every 2 seconds so each time i hit ok, i was able to go 1 step each time. Basically was able to get into settings and do a factory reset which managed to do the trick. restored via TB so minimal setup time again. Would still like to know where i went wrong though but grateful didnt brick it lol (yes i can laugh about it now)
For next time: check the FAQ and stuck threads for info on how to temporarily disable Xposed (with or without a recovery).
The FC was likely caused by a module, so you should ask in the module's thread instead.
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 have the dual sim Exynos version, model number SM-N950F/DS.
I followed this guide 100% as said:
https://www.youtube.com/watch?v=ygcDFTPT248
Root is not properly working. Unsure why. I rooted using Magisk. When checking the app, it has ticked both latest and installed version V16.4. When checking safety net option, both are ticked.
Adaway even after rebooting says ''rooted Android required'' . Root explorer not working also. The only thing I got working and only after rebooting it worked was Titanium backup. After rebooting I was prompted to give root access which obviously I did and it works fine.
However, other apps requiring root access do not prompt me to grant it root access and immediately says ''no root'' .
Any suggestions? Thanks.
Ps. I keep getting this annoying notificaiton on the taskbar saying ''Security notice. Unauthorised actions have been detected. Restart.'' . How do I get rid of this notification? I restarted twice yet it keeps popping up.
And now for no apparent reason I am stuck on the Samsung logo, phone is not booting up. The top left blue LED is flashing but the phone is not booting. Please help.
^ I managed to fix my device, like always I was running an older version of TWRP!! Happens every time with every phone regardless!
From one of the threads, I downloaded the very latest recovery and flashed it via ODIN. Voila! Installed one of the Note 8 roms and perfect. Everything working fine.
Why is it if using a slightly older recovery nothing works? I am unable to even format/wipe, install roms, nothing...