For those who had the same trouble that I had, here's my experience.
Uninstall Recovery by clicking the corresponding button on Safestrap app.
Uninstall Safestrap (I used the root uninstaller pro, but i guess that the standard uninstalling process should work).
Shut down the phone and turn it on again.
Unroot your phone
If the process doesn't reboot your phone, shut it down and turn it on again. Try to use an app that requires su to be sure that the phone is unrooted.
Root your phone.
If the process doesn't reboot your phone, shut it down and turn it on again. Try to use an app that requires su to be sure that the phone is rooted.
Install Safestrap
Install Recovery again.
.
The next time you reboot your phone, the Safestrap boot menu should be avaliable to use.
Important Notes:
I've used DoomLord root toolkit to root my phone. Use the same interface or metod to unroot your phone.
DoomLord Root ( http://forum.xda-developers.com/showthread.php?t=1321582 )
DoomLord Unroot ( http://forum.xda-developers.com/showthread.php?p=18879974#post18879974 )
If you used Super one click, Pete's root tools, etc., be sure to use a interface that is compatible with the rooting interface you've used.
Scenario:
After installing several apps that require su acess (Link2SD, Uninstaller Pro, Titanium Backup), my phone couldn't boot on safestrap anymore, loading the Stock ROM every time it was turned on.
Using the Android Recovery, by pressing the key "m" while turning on, and using the menu "BP Tools", didn't gave me acess to Safestrap to.
I hope that it can help.:good:
Related
Helllo! Got a brazilian I9000B with the digital TV, did a sucessfull root using BackfireNL's update.zip. All was well untill I installed ROM Manager from market and told it to install ClockWork recovery. When it rebooted I told it to apply update.zip and it kept rebooting into recovery mode again without doing anything (and without booting to clockwork) so i selected reboot phone.
After it got back, I noticed that adb shell wont connect to the phone anymore, wifi wont connect and all apps that require root wont work (titanium backup says it was unable to acquire root privileges, for example) even they asking for root and I granting it to them. I have no clue on how to restore everything back to normal, tried unninstalling rom manager but didnt do anything. Tried rooting again, and no luck either. Thanks in advance for the help!
I would suggest that you go into recovery and select Factory Reset and then reboot. Note you will lose all your apps and data.
Thanks for the reply! I just did it, factory reset, cache, multiple times, but the issues are still there. Any way I can put my stock recovery back?
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
Well....i updated to the .905 OTA file and i can't boot into the Safestrap recovery, although it appears i still have root as apps that need root still function and i see the 'granted super user permissions' notice..
I was going to flash the new Eclipse 3.0, but no luck getting into Safestrap...
Little help?
Same problem here. Power down. Hold both volume up and down while powering up. Fastboot menu should come up. Press volume down to the last option BP Tools, then volume up to enter the selection.Mine reboots into safestrap. You'll need to uninstall and reinstall safestrap. works like normal now.
Sent from my DROID BIONIC using xda premium
you probably just need to reinstall. you should still have a safestrap icon in your app drawer. open it and hit install safestrap. for whatever reason it gets removed during updates.
looks like i've lost root with the .905 update. Trying to update the Superuser binary, on 'gaining root access' it fails. Is there any way to restore root access without connecting to a PC? Don't have a USB cord with me at the office...
papasmurph said:
looks like i've lost root with the .905 update. Trying to update the Superuser binary, on 'gaining root access' it fails. Is there any way to restore root access without connecting to a PC? Don't have a USB cord with me at the office...
Click to expand...
Click to collapse
No. You need a pc.
thanks...
Strangely enough...or maybe its not strange and i just don't know enough...when i switch to my 'SAFE' system Eclipse ROM, i still DO have root access. i didn't know that was possible...?
papasmurph said:
thanks...
Strangely enough...or maybe its not strange and i just don't know enough...when i switch to my 'SAFE' system Eclipse ROM, i still DO have root access. i didn't know that was possible...?
Click to expand...
Click to collapse
Didn't think that was possible....strange....maybe you so have root its just.....weird....
Sent from my DROID BIONIC using XDA
Your safe and unsafe systems are completely separate. When you updated to .905 and lost root on your unsafe system, your safe system was still sitting there, rooted and waiting. As long as you still have your 3rd party recovery installed, you're rooted (as far as I'm concerned). For the stock ROM to be rooted, just run motofail.
I lost root with .905 safe strap would still show at boot but would black screen if selected.
you just need to reroot, with motofail.
Stuck in Stock Recovery WITHOUT use of power button
Recently went about flashing custom rom to phone and ended up in the Stock recovery menu, of coarse without the use of buttons i cant get anywhere... also as battery is internal cannot remove. so at the moment is essentially a brick. I recall being able to use a ADB command or something to reboot from recovery but cannot recall what i was or from where it came... any help would be appreciated.
Also on a side note: is TWRP compatible with P7?? or alternatives???
Stuck in custom recovery,only fastboot w/c i can access
Jarvie said:
Recently went about flashing custom rom to phone and ended up in the Stock recovery menu, of coarse without the use of buttons i cant get anywhere... also as battery is internal cannot remove. so at the moment is essentially a brick. I recall being able to use a ADB command or something to reboot from recovery but cannot recall what i was or from where it came... any help would be appreciated.
Also on a side note: is TWRP compatible with P7?? or alternatives???
Click to expand...
Click to collapse
i have also thesame problem...mine started when i click the kingroot,,,its because i have rooted my device twice . i taught i succesfully unroot the kingroot....and then root again with mobilego which have the supsersu icon at finished.....succesfully rooted but the su binary is requesting to be updated and when i do it itis always fail to update,,but supersu succesfully grant any rooted apps that i download...working smooth just before i press the kingroot for to im about to uninstall it,,then the problem begins...now all i can access is the fastboot mode..adb shell cant recognized my phone.... HELP,,HELP HELP.....HEEEEEEEEEEEEEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPPPP PLEEEEEEEEEEEAAAAAASSSSSSEEEEEEEEEEEEEEEEEE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
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.