Database Develop

[Q] Aw Crap. My phone wont factory data reset. Help

A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?

It looks like I need to reflash the stock recovery image. I believe I have that (as long as the stock recovery is the same for all moto x phones (verizon, sprint, tmo, att, etc).
The problem I am having now is that I don't know how to flash the stock recovery image. All the instructions that I find require the phone to be in fastboot mode, but I have a locked boot loader....so. ..wud am I supposed to do??

dzlvs8 said:
A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?
Click to expand...
Click to collapse
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.

_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.

_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?

dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Click to expand...
Click to collapse
Well your phone is technically rooted when you boot normally, but you don't have write capabilities to /system which is why nothing is sticking. You need to boot the phone into recovery mode to make those changes, and then reboot normally to use them. To boot into the recovery mode with write protection off you need to power your phone down, and power it back up while holding volume down. That gets you into the bootloader and from there you choose recovery and then your phone will reboot with write protection off. It's kind of annoying to have to do it this way but blame Motorola for locking the phone down as well as they did.
To flash the stock recovery back, you need to put the recovery file in your adb folder and then the command is "fastboot flash recovery recovery.img" without the quotes, but if you are unfamiliar with adb I don't recommend doing it. You can just flash the whole stock image with RSDLite and start from square one. I've not personally used RSDLite but here is a video tutorial for you- http://forum.xda-developers.com/showthread.php?t=2446515

dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?
Click to expand...
Click to collapse
also just a quick note:
"adb reboot recovery" will boot you into recovery/writeable system
"adb reboot bootloader" will boot you into fastboot for using rsdlite which is all described in the instructions given by metalhead

Custom binary blocked by reactivation lock

RESOLVED!
Turns out I had reactivation lock enabled.
Took my the whole damn day to figure this out, lol.
So, if anyone is a noob like me and ends up with this message on their screens, just go to Settings--> Security , and uncheck reactivation lock.
Now onwards to flashing heaven!
EDITED TO OP: RESOLVED
I'll post this in the OP since this is the trouble I need resolving now, and the old OP has been resolved:
NEW PROBLEM:
Sorry to bump this thread, but I keep getting this error when trying to boot into recovery.
I tried to re-flash twrp via Odin and via the twrp app with no success. The phone will boot loop into this message until I pull the battery off.
When trying to Odin twrp recovery it always ends up saying fail.
I wanted to flash a new rom and I can't because of this.
Current rom is firekat v4.
Thanks for any help.
EDIT:
I was able to flash stock recovery, but twrp still fails.
I'm really lost here.
OLD OP/RESOLVED:
So, I was trying to update super su, and I chose twrp, because I have it installed.
The phone rebooted into a yellow triangle (different from the one in download mode), with the title of this thread displayed on the top of the screen.
It kept looping into this message, I could only get it into download mode.
I had to try to Odin twrp recovery again, and even though it failed, at least it got me out of the boot loop.
Phone's working fine, but I think Knox is to blame here.
I tried updating super su by choosing the "normal" option and everything worked.
But since I have twrp,shouldn't it have worked with the twrp option?
Sent from my SM-N910T using Tapatalk

No. Normal is the normal method. TWRP is for those systems that fail when using the normal method.
Sent telepathically

MarkP80nj said:
So, I was trying to update super su, and I chose twrp, because I have it installed.
The phone rebooted into a yellow triangle (different from the one in download mode), with the title of this thread displayed on the top of the screen.
It kept looping into this message, I could only get it into download mode.
I had to try to Odin twrp recovery again, and even though it failed, at least it got me out of the boot loop.
Phone's working fine, but I think Knox is to blame here.
I tried updating super su by choosing the "normal" option and everything worked.
But since I have twrp,shouldn't it have worked with the twrp option?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
It pays to read before mashing buttons. The dialog that displays the Normal and TWRP/CWM buttons explains the difference. You're supposed to use Normal and only use TWRP/CWM if Normal fails.

Thanks guys, I feel so dumb now, lol.
Happy thanksgiving.
Sent from my SM-N910T using Tapatalk

Copied this post and pasted to OP.
Sent from my SM-N910T using Tapatalk

[Q] E: Cannot be found when factory resetting

Hi all,
I really need your guys help. Out of nowhere today my phone restarted and then got stuck in a bootloop. When I went into recovery, it gave me the "android is updating" pop-up. I knew there was no update and within 20 seconds or so it said "no command". I went through to wipe the cache, and after rebooting it back up, strangely it didn't give me the "android is updating" screen that occurs after wiping cache. I went ahead and tried to factory reset through recovery and everything was fine until I got a msg "E: could not mount (file or directory could not be found) or something a long those lines. I'm assuming the EFS is fried? I rebooted it after and even at the "Welcome Screen" it started boot looping again. I'm stock lollipop unrooted. I never rooted this phone or flashed any ROMs. I called T-Mo and they will send me a replacement but I still want to see if this can be fixed. I also don't have a replacement phone so..there's that. Would anyone be able to help?
Edit: The only thing I haven't tried is flashing the stock firmware via odin. Would this trip the knox counter though? I really want to avoid that especially since I am having these issues and I don't want tmo/samsung to think I caused this issue.

Bad phone. Ur new phone will be good to go.
BAD ASS NOTE 4

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.

My Galaxy S4 active (AT&T) is bricked, tried to restore it

This is my backup phone so I don't care for the data that is on it and just want it working again. It was rooted before and I needed it unrooted in order to download an app that was blocked by root detection. I tried uninstalling the root using Super SU in its settings, when I restarted my phone it just freezes at the AT&T white screen.
I'm still able to go into the boot recovery menu, I tried putting on the I537UCUCOC7 (5.0.1) firmware found here (https://forum.xda-developers.com/showthread.php?t=2629093). I downloaded it, extracted the zip, and renamed the file "update.zip" and put the file on a microSD then in the recovery boot menu I went to install from external and selected the update.zip. It sorta kinda looked like it accepted it but I get a red error message about the sideloader and I'm still stuck at the white screen when it boots.
What else can I do from here?
P.S. I already tried wiping the cache and data/factory restore options and that didnt work.

Is there anything else that can be done?

I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.

Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop

RemixDeluxe said:
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Click to expand...
Click to collapse
alex4cta said:
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4-active/general/guide-update-to-i537-att-firmware-t2835481