Related
My boss went to take the lollipop ota today and his phone is rooted now it boots to twrp (I did not know it was rooted) until I seen the twrp recovery it's stuck looping back into twrp everytime it's reboots NEED HELP ASAP
Thanks in advance
chazla86 said:
My boss went to take the lollipop ota today and his phone is rooted now it boots to twrp (I did not know it was rooted) until I seen the twrp recovery it's stuck looping back into twrp everytime it's reboots NEED HELP ASAP
Thanks in advance
Click to expand...
Click to collapse
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.
I found it after doing what I should have done first and took the time to search thanks again
So I tried two ways one was directly from Odin and my watch rebooted into standard recovery and then wiped something then rebooted and I had to activate and pair it all over again, then I tried SkipSoft's method and it just led me around in circles, because of the reboot to recovery flash permanent-recovery zip and not actually in TWRP just in standard recovery again.
Someone help or point me to another method if there is one, I wanna flash Null_ rom and fully unlock this watch.
Once I got custom recovery installed and sticking I could root and everything else on my own.
On firmware version V700XXUAMK7
Did you run the adb command from the little box thingy underneath 'note 2' in the instructions?
The adb cmd line? Don't think tried that yet, but it was rooted beforehand, so I thought I'd be safe it did say it happens if ya aren't rooted, now I'm fighting tooth and nail after custom recovery failed to connect it to my phone again, sadly you'd have thought samsung would've made pairing easier than this crap, I might as well be trying to pair a iWatch to a Samsung that's how full of fail their pairing procedure is. It shouldn't take 30 damn minutes of trying and fails and a few reboots of each device to do this.
That's the one! I think I thought the same as you when I flashed twrp. The install bit of the statement must refer to twrp not root and it should read probably won't install if you don't run this command.
Gear manager is, in my opinion, a POS. From reading it doesn't like being updated. I think that there's some corruption in the data or cache of one of the components that make up gear manager when it updates which can cause problems like connection and massive battery drain. The method I've used before is to use es file explorer to clear the cache and data of all gear component apps (9 on my phone) and delete them, leaving gear manager proper to last. Then reinstall gear manager again. This is a big pain on null because it wipes a lot of stuff of the watch so it's a good idea to have titanium backup on your watch.
Although I'm about ready to give up on this POS and resell it I've never seen something so dammed complicated to pair up and sync I'm still trying and the monkey developed thing is so behind its giving me old pair codes minutes after trying to pair then reporting incorrect pair code, well no duh.
Sent from my SM-N915T using XDA Premium 4 mobile app
Rather wait till the end of the year and get the Rufus Cuff, at least it wouldn't be ruined by Samsung failed coding.
Sent from my SM-N915T using XDA Premium 4 mobile app
Now it seems as though I'm stuck decided to try the latest UK Version of Tizen OS loaded it in Odin 3.09 into the AP Slot pressed started and then damn Odin decided to pop up with a error and close out in Windows, now if I try anything still download mode and reopened Odin 3.07 or 3.09, but it never fully installs I'm in the emergency download kies recovery screen.
Is it possible to install a Odin'ed firmware from here, from what I've learned of the screen/area of recovery, it's the same thing as download mode. I tried the latest Tizen OS again and all it did was sit forever at zImage area of flashing.
Just TWRP installed and to stick, dunno how, but I sideloaded SuperSU since I was already rooted and had KingUser then I tried ADB which didn't appear to work so I tried SkipSoft's custom recovery method and I guess that seemed to work for me, cause now I'm happily on Null_ 23.
Hey everybody,
i hope so much, that anyone can help me. After i installed the recovery TeamWin (TWRP) (it was successful), i tried to flash Xposed Framework manually, i got again an massage "it was successful". But after that i can not start my Samsung Galaxy S5. It shows me only the Samsung Logo and nothing happened. Of course i tried via TeamWin an factory reset but i still can not boot my smartphone (Stop at the Samsung Logo). My S5 ist rooted, i`m using 5.0 (lollipop). Version of the TeamWin was 2.8.7.0 and of the Xposed Framework "xposed-v74-sdk21-arm". Has anybody an idea? I would be very happy. Should i delete the TeamWin recovery? But how? I want to install the standard recovery of Samsung, but how to do this? Where can i find the original Recovery from Samsung?
Xposed isn't supported on latest Android versions (r23). You should just remove Xposed from your phone, by using this tutorial:
Code:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Deadclysm said:
Xposed isn't supported on latest Android versions (r23). You should just remove Xposed from your phone, by using this tutorial:
Code:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Click to expand...
Click to collapse
Thank you, but i cant find the xposed folder...because i made a factory reset
Just delete the files and folders that you can see (those which are Xposed related). It should fix your problem.
Or just flash ovet your rom again (dirty, without wiping).
Sorry it took long time for me to answer.
Edit:
Read sticky, there's a script that uninstalls it automatically. This should work 100%
always make nandroid backup before flashing
Having the same problems
So I'm having the same problem. The Framework says it installs correctly, but after reboot, device gets stuck at the Samsung screen. I don't understand the comment android r23. I'm looking at the build info and I don't see this anywhere. Some explanation or assistance would be great.
I'm not sure why sdk 23 was even mentioned as Lolliopo 5.0 is sdk 21.
@LieberKerl, you got the xposed-v74-sdk21-arm.zip from Rovo89's thread, correct? If so this will not work on stock Samsung Touchwiz ROMs as mentioned in the first post of that thread.
There is no Xposed that will work on a stock Samsung Touchwiz ROM, it must be deodexed first and if you have a deodexed ROM, you need arter97's unofficial Xposed from this thread: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463.
If you don't know what deodexed is, there's a bit of reading ahead of you. If you don't want to deodex your Lollipop 5.0 ROM, then you're out of luck.
It takes longer to boot after the install, how long did you leave the samsung boot logo up? it took nearly 15 mins to boot after rom install and around 5 mins after xposed framework. I went through alot of hassle just to discover i was impatient.
Reflash stock ROM with Odin.
after flashing in my unite 3 notification bar disappeared and phone is restarting again and again
Nerotech11 said:
It takes longer to boot after the install, how long did you leave the samsung boot logo up? it took nearly 15 mins to boot after rom install and around 5 mins after xposed framework. I went through alot of hassle just to discover i was impatient.
Click to expand...
Click to collapse
Happened to me too on an Oukitel C4. After flasing it needs quite some time to boot.
Cannot Install Xposed in Samsung Galaxy S6
I have the same issue with a Samsung Galaxy S6. I tried installing "xposed-v87-sdk23-arm64.zip" using TWRP. But Every time I do it the phone either goes completely black or shows the Samsung Logo flickering permanently. To fix this I need to go into TWRP again and install "xposed-uninstaller-20160829-arm64.zip". I tried leaving the phone with the black screen/logo flickering for over 1 hour hoping it might be installing something but the only way to turn the phone back on is with the uninstaller.
I thought that it might be due to not having OEM unlock enabled, but I cannot find the option in "developer tools". Then I tried to do it through ADB command lines but when I enter the command "fastboot-windows oem unlock " it gets stuck with the message "waiting for device". So I also tried installing PdaNet both on my windows 7 PC and the phone itself (Android 6.0.1) and I made sure I have the phone drivers installed on my PC.
All I want is to use Xposed modules on my Galaxy S6. Is it even possible? If so, what should I do?
I appreciate any suggestions.
Thank you.
InfiniteSegovia said:
I have the same issue with a Samsung Galaxy S6. I tried installing "xposed-v87-sdk23-arm64.zip" using TWRP. But Every time I do it the phone either goes completely black or shows the Samsung Logo flickering permanently. To fix this I need to go into TWRP again and install "xposed-uninstaller-20160829-arm64.zip". I tried leaving the phone with the black screen/logo flickering for over 1 hour hoping it might be installing something but the only way to turn the phone back on is with the uninstaller.
I thought that it might be due to not having OEM unlock enabled, but I cannot find the option in "developer tools". Then I tried to do it through ADB command lines but when I enter the command "fastboot-windows oem unlock " it gets stuck with the message "waiting for device". So I also tried installing PdaNet both on my windows 7 PC and the phone itself (Android 6.0.1) and I made sure I have the phone drivers installed on my PC.
All I want is to use Xposed modules on my Galaxy S6. Is it even possible? If so, what should I do?
I appreciate any suggestions.
Thank you.
Click to expand...
Click to collapse
Most likely your issue is caused because you did not install the correct framework version. You need the one from wanam. Just search for "Xposed Samsung wanam" and you'll find your answer.
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...