So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay. My problem is that I still get error messages constantly after boot up and the simplest tasks can take hours (not to mention I can't use phone, contacts, messaging). I have seen all over the web (and XDA) about unrooting the phone and retuning it to stock. I was thinking that I could unroot, then reroot my Relay and that will solve my problem.
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Please help me as I anxiously await using my new phone without the extra bloatware!
Thank you,
RockinRita
RockinRita said:
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Click to expand...
Click to collapse
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Bobby Tables said:
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Click to expand...
Click to collapse
Without the stock files wouldn't Kies be pointless?
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Pushing on a Relay
RockinRita said:
So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay.
Click to expand...
Click to collapse
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you
used adb push, but how?
Thanks,
Lou
scopedial said:
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you used adb push, but how?
Thanks,
Lou
Click to expand...
Click to collapse
I copied the files from my rooted HTC Desire Z/ T-Mobile G2 to a spare SD card I have and then I inserted that card into my Relay and started it up. It took me a few hours to get passed all the error messages that constantly pop up. And then I went into my files, external SD and moved the files over to the system folder on the Relay. After several reboots, the error messages still are coming up which I why I need to unroot it and reroot it.
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You may have just saved me, Magamo! Thank you for saving them to Drive! Once I get on my old slow Dell laptop (i'm on my Chromebook now- which unfortunately doesn't support most things) I'll try to flash your files and update you here since I cannot comment on your post as I have not posted enough myself.
Stock ROM Restore Method I Used
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
I'll be honest, you've got me on this one. I've never used ODIN, and am not well versed in its use. But yes, this is sounds like a more technical way of doing it without the CWM flashables I've mentioned. -- Impossible in some situations. For example, my fiancee's phone's USB port has died for all purposes other than charging, So if I'm to send it in for a warranty repair, I'll have to use the method I posted.
Confused here
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
RockinRita said:
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
Click to expand...
Click to collapse
If you don't have CWM, or some other custom recovery running on this, how did you get root in the first place? The easiest way to get root is to use heimdall or ODIN to flash CWM or another custom recovery, then flash Superuser or SuperSU using your new custom recovery.
The .zip files I linked are only meant to be flashed through recovery. Not Kies, not ODIN, not any other method.
Got it!!
With the help of this site (http://www.celldekho.com/how-to-unroot-samsung-galaxy-s-relay-4g/) and the file it linked to on rapidshare, along with your tip Magamo, I was able to unroot my Relay successfully. I'll reroot it later when I have the time and make sure not to delete important files LOL Thanks so much for the help!
Related
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Me[kk]A said:
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Click to expand...
Click to collapse
which cwm did u use
wich su file did u use
read this on rooting http://forum.xda-developers.com/showthread.php?t=1340526
but use this cwm http://forum.xda-developers.com/showthread.php?t=1566613
Me[kk]A said:
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Click to expand...
Click to collapse
download procedure?
just put superuser on sd and install from cwm.
no root access means no su binary's installed. su binary's will not install from the superuser in the market that's just a front end.
wouldn't you also require busy box and then fix permissions using rom manager?
SeraldoBabalu said:
wouldn't you also require busy box and then fix permissions using rom manager?
Click to expand...
Click to collapse
no. busy box has nothing to do with su. and rom manager sucks and you will have nothing but trouble if you use it. just download odin and cwm and superuser thats all you need to root that expensive phone.
Try the super user file located here: http://forum.xda-developers.com/showthread.php?t=1565126
I had a similar issue as you and the su in the link worked fine. If it fails keep trying, took me like 3 tries.
Sent from my SAMSUNG-SGH-I727 using xda premium
vincom said:
which cwm did u use
wich su file did u use
read this on rooting http://forum.xda-developers.com/showthread.php?t=1340526
but use this cwm http://forum.xda-developers.com/showthread.php?t=1566613
Click to expand...
Click to collapse
I used this guide: http://forum.xda-developers.com/showthread.php?t=1340526
but used the newest tar file provided on one of the rogers ics rooting threads.
As nothing is visibly wrong at this point, could I simply retry to root? Or should I wipe everything first?
So i tried to reflash again and use the new hercules file in odin.
All went well until I went into cwm recovery to make a back up, it said the it couldn't mount and aborted.
I backed up onto the SD card and it proceeded, however, when trying to load the superuser file from the external sd, it also said it couldn't mount, and aborted there.
any way around this?
Me[kk]A said:
So i tried to reflash again and use the new hercules file in odin.
All went well until I went into cwm recovery to make a back up, it said the it couldn't mount and aborted.
I backed up onto the SD card and it proceeded, however, when trying to load the superuser file from the external sd, it also said it couldn't mount, and aborted there.
any way around this?
Click to expand...
Click to collapse
dont use a touch recovery, flash a non touch recovery then install superuser. or put the superuser zip on the emm(internal sd).
popcorn900 said:
dont use a touch recovery, flash a non touch recovery then install superuser. or put the superuser zip on the emm(internal sd).
Click to expand...
Click to collapse
use this touch from tpmullan http://forum.xda-developers.com/showthread.php?t=1566613
u used this one from sk8erwitskil, u have to mount the sdcard first, but he has fixed it now(in testing) http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils
dont read my sig
vincom said:
use this touch from tpmullan http://forum.xda-developers.com/showthread.php?t=1566613
u used this one from sk8erwitskil, u have to mount the sdcard first, but he has fixed it now(in testing) http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils
dont read my sig
Click to expand...
Click to collapse
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Me[kk]A said:
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Click to expand...
Click to collapse
weird, which method did u use to flash cwm
where is backup located, int or ext sdcard, which cwm version did u make backup
what do u mean it wouldnt read superuser, maybe redownload su and check the md5, running su in cwm has to b done a few times until it states that it has completed sucessfully
edit:try to mount sdcard from within cwm in "mounts and storage/mount sdcard" also mount emmc, i never had to do that but it might b that u have to do it once
Me[kk]A said:
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Click to expand...
Click to collapse
well if you would just try a non touch recovery you might be surprised.
http://forum.xda-developers.com/showthread.php?t=1725221
this recovery works and this is all the help i can muster up. so now if you cant figure it out then i guess you shouldn't be flashing phones.
I have the same phone this is what I did
Flash phone with CWM use this one
Clockworkmod Touch 5.8.1.3 Odin tar http://forum.xda-developers.com/show....php?t=1566613
Then wipe data/factory reset, format- system, data and cache, and clear the partition and dalvik caches, do that to all of them 3 times each, using touch cwm.
Then odin ICS download it from here http://www.sammobile.com/firmware/
(make sure only Auto Reboot is checked nothing else)
Once the phone loads go through the setup then leave it alone, let it sit for about 20min then flash back the CWM. Then download Superuser from here and put it on the root of your SD card then flash it in CWM if it fails just keep doing it until it works, it worked the second time for me.
Once superuser is installed install busybox from the market and everything will work.
This method worked perfect for me I was having the same problem like you. The key is to wait about 20min after you flashed ICS before you do anything else.
Hope this helps you.
Well, the final superuser file worked, everything backed up perfectly.
Wanted to thank you all for you assistance. Vincom, if I knew who you were in Bolton, id buy you a beer, as I'm in your town 3 times a week.
lol Cheers everyone.
Me[kk]A said:
Well, the final superuser file worked, everything backed up perfectly.
Wanted to thank you all for you assistance. Vincom, if I knew who you were in Bolton, id buy you a beer, as I'm in your town 3 times a week.
lol Cheers everyone.
Click to expand...
Click to collapse
cool, what was the solution? bad download
vincom said:
cool, what was the solution? bad download
Click to expand...
Click to collapse
I'm not entirely sure. After not being able to back up, I grabbed an external sd, put superuser on that.
The back up went through with no problems. Also, superuser installed on the 2nd try and all went well with permissions from there.
Friend of mine had picked a zip file labelled "root" to use with Odin, and I'm suspecting the tar files I had attempted with in the past weren't correct and this file was.
Either way, I have lots more reading to do to fully understand what is available to me now. Busybox, nandroid, ROM toolbox installed.
iv flashed my phone so many times that flashing stock and rooting seem tedious to me. glad you got it rooted, now make a nand backup so you don't have to do it again.
my 32 gig sd is filled with nand dumps lol i don't even have a game on it to play.
Hi,
I'm thinking about rooting my Note 10.1 (mostly because I want to use DicertoryBind/Link2SD) via ClockworkMod Recovery.
My questions:
I won't receive any OTA updates, cause the status will be custom, right?
I want to stay on stock FW, what can I do to update my tablet if there is a new OTA:
Can I directly flash the FW from sammobile with odin or are they not campatible with cwm? Would that mean that every time there is a new OTA, I have to unroot, flash back to stock recovery, get the OTA, flash back cwm and root again?
Isn't there a way to flash the update while keeping all my data (just like normal OTA does) and root ?
Thanks!
Kamairo said:
Hi,
I'm thinking about rooting my Note 10.1 (mostly because I want to use DicertoryBind/Link2SD) via ClockworkMod Recovery.
My questions:
I won't receive any OTA updates, cause the status will be custom, right?
Yes
I want to stay on stock FW, what can I do to update my tablet if there is a new OTA:
Can I directly flash the FW from sammobile with odin or are they not campatible with cwm? Would that mean that every time there is a new OTA, I have to unroot, flash back to stock recovery, get the OTA, flash back cwm and root again?
You can flash using ODIN, but you will need to re root the device, also chances are you will not lose data but in rare cases you will need to do a factory reset which will mean you lose all your data.
Isn't there a way to flash the update while keeping all my data (just like normal OTA does) and root ?
Above answer should answer this also but you will need to re-root the device
Thanks!
Click to expand...
Click to collapse
Hope this answers all queries
You can flash using ODIN, but you will need to re root the device, also chances are you will not lose data but in rare cases you will need to do a factory reset which will mean you lose all your data.
Click to expand...
Click to collapse
Okay, that means I download the firmware from for instance sammobile, flash it using ODIN (will that be PDA only, like flashing cwm?), and then re root means install superSU again from cwm or installing cwm completely new?
*edit* Thanks for the sticky!
Yes you can use this post to know how to install using odin http://forum.xda-developers.com/showthread.php?t=2080366
You do not require CWM to root you can use the exynos patch apk to root you can download the apk from here
http://forum.xda-developers.com/showthread.php?t=2050297
samir_a said:
Yes you can use this post to know how to install using odin http://forum.xda-developers.com/showthread.php?t=2080366
You do not require CWM to root you can use the exynos patch apk to root you can download the apk from here
http://forum.xda-developers.com/showthread.php?t=2050297
Click to expand...
Click to collapse
Hey, thanks so far, I just installed CWM, everything went fine, but if I look at the system status it still says "offical", does that mean I can receive OTA's? Or won't that work cause of CWM?
Also I believe before it didn't say "official" but "normal".
*edit* okay, nevermind, after a reboot it sys now "custom"
Since you have rooted your device you can also use Mobile ODIN to flash the roms from sammfirmware directly on your note 10.1. You just make sure everroot is ticked but if you think you might loose root then have both the CWM.tar file saved on your device, its a tiny file so no real space lost or if you don't care about CWM but want root access then keep the exynosexploit.apk on your device. I have everything I need on the sd card in case I cant get to a PC. Much better when I'm not tied to the PC...
ultramag69 said:
Since you have rooted your device you can also use Mobile ODIN to flash the roms from sammfirmware directly on your note 10.1. You just make sure everroot is ticked but if you think you might loose root then have both the CWM.tar file saved on your device, its a tiny file so no real space lost or if you don't care about CWM but want root access then keep the exynosexploit.apk on your device. I have everything I need on the sd card in case I cant get to a PC. Much better when I'm not tied to the PC...
Click to expand...
Click to collapse
Thanks so far, but theres one question left: From what you've said I think it's possible to flash with odin or mobile odin while CWM is still installed, what will happen to CWM after the flash? Is it completely gone (stock recovery comes with the firmware?!) or does "re root" only mean that I have to reinstall superSU with CWM?
You will go back to stock recovery but you might retain root if you ticked everoot function....
As I said earlier, you can reflash CWM onto your Note using mobile ODIN if you have the CWM.tar file stored on your device...
+1 for Mobile Odin if you're wanting to stay stock.
Use Exynos Abuse to root the first time.
Install Mobile Odin pro.
Backup your EFS partition off the device.
Install CWM using Mobile Odin and make a nandroid backup.
Back up apps with Titanium if required.
Download the new stock from you want and use Mobile Odin to install with Everoot selected.
Use Mobile Odin to install CWM.
Simplest method I've found by far.
Sent from my GT-N7100 using xda premium
After rooting with exynos abuse root, can you just do a factory reset to make you stock again to get OTA's?
I don't believe so (prepared to be corrected) but if you reinstall the stock rom without Everoot ticked and factory reset you'll be back to stock unmodified.
Sent from my GT-N7100 using xda premium
Never tried but I don't think so, The OTA checks for an unmodified system and even though stock recovery says its official the status in settings is "Custom".
What if I'm on the stock rom (never went custom) and stock recovery. All I did was root? Would a recovery restore allow me to get OTA's?
if you are on stock recovery then why would you restore recovery.
Yes if you are rooted only you will receive OTA if you are on the orignal rom (rom from country which note was purchased irrespective of the version you are on)
samir_a said:
if you are on stock recovery then why would you restore recovery.
Yes if you are rooted only you will receive OTA if you are on the orignal rom (rom from country which note was purchased irrespective of the version you are on)
Click to expand...
Click to collapse
That is my situation, exactly. So, I can take OTAs in my present situation? I used #2 root option from zedomax. I haven't changed anything or used a custom rom. All I want to do is get current on my updates, and retain root and CWM.
Should I also use TriangleAway, and at what point? Thank you.
Apologies to the OP, but I've been waiting for a chance to resolve this.
If you used method 2 you have replaced the stock recovery... That's what CWM recovery means...
You're flash counter will now be one and need to be reset using triangle away. No OTA for you...
ultramag69 said:
If you used method 2 you have replaced the stock recovery... That's what CWM recovery means...
You're flash counter will now be one and need to be reset using triangle away. No OTA for you...
Click to expand...
Click to collapse
Thank you.
I am new to this. I have a rooted nexus 5. It is stock rooted with TRWP recovery. I don't have a custom ROM. When the newest update is available, am I safe to update?
ILowry282 said:
I am new to this. I have a rooted nexus 5. It is stock rooted with TRWP recovery. I don't have a custom ROM. When the newest update is available, am I safe to update?
Click to expand...
Click to collapse
Since your post was made today, and the update was released yesterday I'm assuming you are thinking that you will be getting the update over the air? You won't. When you have a custom recovery (TWRP) you won't get OTA's.
But don't be disheartened, not in the LEAST. Unless you've removed or altered the default system apps (you would know if you did) all you have to do is download the update to your phone, boot into TWRP, flash the update, and let the phone reboot.
Due to how the OTA updates are rolled out, even if you had not loaded a custom recovery onto your phone, you might not have had it pushed to you for a couple of weeks.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2523217
From what you have described you are "scenario 2". Proceed directly to step B. Like many people, I was also step B. It is easier than making toast.
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
ILowry282 said:
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
Click to expand...
Click to collapse
1. If you flash a custom ROM via TWRP it is generally recommended you do a clean wipe beforehand (and before doing that, obviously create a backup). There are cases where you can go straight to flashing without wiping, which is called a dirty flash. Although this is used when you're flashing an updated version of the ROM you're currently running. Following instructions under Section B won't cause you to lose data.
2. You won't lose root because ROMs will generally take this into account. However, if you do happen to lose root, just download and flash SuperSU and you're back on track.
3. Just flash the zip file.
ILowry282 said:
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
Click to expand...
Click to collapse
The first part of the reply above is certainly correct, (the rest is also, but I'm just speaking to the first part of it) but I feel it is just going to confuse you.
You did not flash a custom ROM, you flashed a custom RECOVERY. Two different things. When you copy the update onto your phone, in the form that exists in the thread I linked earlier, it is not an entire image. It is an UPDATE to the stock image, which you are already using. As for your concern of losing root, it shouldn't be a concern. As was mentioned in the reply above mentioned, while you are in recovery you can simply just flash SU again.
In fact, I'd be willing to bet the file to flash SU is still on your phone.
As for me personally, I happened to have unlocked the pro version of SU (because why not...it's only $2.50 and I like the app) and just toggled the "survival mode" option. But even if I had not, it would have been a very small thing to loading SU again.
In short, don't worry about losing root. When you first rooted this phone, most of the steps involved were not in rooting the phone, but in unlocking the bootloader. Loading this update has nothing to do with that, so in your case, since you didn't flash a custom ROM (Such as CyanogenMod) and you didn't make any modifications to the system apps...quite literally all you have to do is copy the stuff onto your phone, load into TWRP, fire up the update, and either fire up SU, or have survival mode already enabled, and reboot the phone.
(and no, you don't have to unzip the file pasted in the thread, just copy it directly) The instructions in that thread are really simple, and that's probably giving you a bit of pause, but seriously, it really is that simple in your case, as it was mine.
So I updated but lost root. How do I flash SU?
ILowry282 said:
So I updated but lost root. How do I flash SU?
Click to expand...
Click to collapse
Do you still have custom recovery cwm or twrp? If so download su zip from either of those posts and flash in recovery if not you can flash recovery with adb or flashify and then flash su zip.
Sent from my Nexus 5 using Tapatalk
Worked perfect. Thanks
How do you unroot the GS3 and get back to stock unrooted? I am currently just stock rooted. I'm just done with flashing and don't want to worry about something happening to my phone while I'm rooted, and am sick of it not being able to take the VZW update on a daily basis. I understand there is an unroot in the superuser app, is it as simple as clicking that and it will unroot by itself? Is there more I need to do? Thanks for your help!
Bump
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
buhohitr said:
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
Click to expand...
Click to collapse
Thank you. Once you perform either or these methods, can you still root again in the future if you decide to?
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Bump
irl5fan said:
Bump
Click to expand...
Click to collapse
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
irl5fan said:
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
Click to expand...
Click to collapse
You're right, try to search for it in Google. I didn't bookmark anything.
Sent from my HTC6525LVW using Tapatalk
irl5fan said:
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Click to expand...
Click to collapse
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
Sent From V500
Using XDA App
unroot gs3
LiamAtkins90 said:
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
irl5fan said:
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
LiamAtkins90 said:
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
Click to expand...
Click to collapse
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
irl5fan said:
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
Click to expand...
Click to collapse
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
LiamAtkins90 said:
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
irl5fan said:
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
Click to expand...
Click to collapse
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
My model number is SCH-I535. I have used Odin before, but I'll take a look at the guide just to make sure. Thanks for your help!
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
ShapesBlue said:
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
No problem, glad I can help.
Verizon edition Models tend to get overlooked as oppose to International variants which is a shame, I think both should get equal recognition. Not just Sammy Verizon, most Verizon models and also Google Play Edition Model Phones/Tablets get pushed aside.... Crying shame.
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
Everything worked out great, flashed the stock firmware and was able to take the OTA. Thank you so much for your help, it's greatly appreciated!
FAQ section in the 2nd post.
BEWARE OF EVERYTHING! I AM NOT RESPONSIBLE if your phone implodes, aliens take over Mars, don trump starts WW3 and WW4, or your dish washer starts working again from using this guide. Remember: just because it worked for me, does not mean it will work for you, but it might! I recommend having an ODIN copy (.tar file) of the MDL bootloader so in case anything goes south, you can get back to stock and start over from scratch.
IMPORTANT! This guide will show you how to (easily) maneuver around the At&t sgh-i337 on the MDL bootloader as far as root and other things are concerned. This guide is NOT for any other bootloader! Once you have updated past jelly bean 4.2.2 then you will not be able to use this guide!
Now for the good stuff...
So you've just taken your new At&t GS4 out of the box and discovered that you're on the MDL bootloader (like I did)! First you're going to want to root it. You can do this by grabbing a good 'ol copy of towel root (just search the forums here or Google for it). Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you.
Next you may want to install a custom recovery. To do this, you will need to use an exploit file called Loki Doki. Follow this video to take the needed steps to get loki'ed and a recovery installed: https://www.youtube.com/watch?v=VmkL9atpVHw
Yes, I know it installs CWM which is way out of date, if you want to use TWRP go ahead. However, this guide deals with CWM so if you use TWRP you're using it at your own risk and going against the guide! GO WITH THE GUIDE!
However, if you want to update to TWRP recovery then this video by the same guy as in the last video should do it: https://galaxys4root.com/galaxy-s4-...or-verizon-galaxy-s4-with-twrp-v-2-8-4-0/amp/
Once you've got loki lurking around your phone's memory, you're good to install a custom ROM! TA-DA! Awesome how all that worked out isn't it?
How to install a custom (TW) ROM
If and only if you followed the ZedoMax video, you should now have OUDhs CWM Touch Req0very v1.0.3.4 installed. Now would be a great time to boot into it so power off your phone then hold power, home, and volume up at the same time. Hold it! Hold it! Hold it! Release when you see the CWM menu. Now let's Nandroid this hush puppy!
Goto backup and restore and hit backup. It will most likely save it to your internal memory, but you can copy it to SD card later, or just reboot now and move it. We now have a working backup in case your dog eats your homework. After that's done, make sure the ROM .zip file you are going to boot is on your SD card. Now go to wipe cache partition and select yes. Go to Advanced and wipe dalvik cache. Go to wipe data/factory reset and select yes. Goto mounts and storage and select format cache, then select format /system.
NOTE: If you want to keep all your personal data (pics, videos, etc.) then stop here! If you want to completely nuke your phone and start from scratch then select format /data from the mounts and storage menu.
Once you've formatted /system (or did a complete wipe by formatting /data too so now you have nothing), you're ready to install a ROM. Select install zip from SD card from the main menu. Find your ROM .zip file and select it. I used the latest GoldenEye ROM because it has an Aroma installer built in so it pretty much does everything for you once you tell it what you want. Easy!
ROM should now be installed and everything should work ok once your phone reboots out of CWM recovery.
How to boot a custom (AOSP/CM) ROM
WARNING! THIS IS EXPERIMENTAL! Following this may get your ROM booted or not. Do so at your phone's own risk! You could erase stuff on accident!
Place the ROM file on your SD card. Boot into recovery and select wipe cache partition. Then select wipe dalvik cache. Now select wipe data/factory reset. Once all that's done, you will need to format /system and /data. Now goto install .zip from SD card. Select your ROM file and pray to whatever higher power yourbelieve in that it worked. Next you're going to (maybe) need a kernel.
Kernels and Modems
Download a compatible kernel for the ROM you want to use. Boot into recovery and flash the .zip file for the kernel from your internal memory or external SD card. Be sure if you are booting a TW ROM that you use a TW kernel. Same goes for CM and AOSP.
Modems are pretty much universal on the MDL firmware and possibly on others as well. To flash a modem just select the .zip file and flash in recovery from your SD card or internal memory. You can use any baseband modem...MDB, MK3, NB1, OC3, etc.
FAQ Section
What is the MDL bootloader? It's the jelly bean 4.2.2 firmware for the at&t galaxy s4. It's a locked bootloader, however it has a flaw in it that can be exploited by Loki Doki to allow a custom recovery to be installed.
What is Loki Doki? It's something that exploits the flaw in the MDL bootloader allowing you to do things an unlocked bootloader can do. To my best of knowledge, it acts similar to a PlayStation modchip by tricking the bootloader into thinking that whatever you feed it, is authorized to boot.
Can I downgrade my bootloader to MDL if I took the OTA? Only if you're a Samsung or at&t smartphone hardware tech.
Why can't I use Loki on other bootloaders? Because the flaw that loki exploited was patched in the MF3 firmware. With the exception of the MDB bootloader which was the bootloader before MDL.
Do I need motochopper to root my at&t s4? Nope, towel root works just fine to get root on the MDL bootloader.
Why does OUDhs CWM recovery tell me root or recovery may be lost on reboot and want to fix it? I have no idea, I think it's a bug. Just select "go back" until your phone reboots and all should be fine.
Why does your guide say "experimental" for AOSP or CM based ROMs? Mainly because I haven't messed around with any and am basing on how to boot them off my time using the galaxy s2.
Why can't I use TWRP recovery instead of CWM? You can, as I pasted a link to get TWRP installed in my guide. It's just I based my guide around CWM because that's what I have always used. Do note that TWRP is different, so you'll have to figure out how to wipe and install the ROM property.
What's the difference between CWM recovery and TWRP recovery? Nothing really, except the UI and how they handle files and things. Due note that CWM recovery has been discontinued, while TWRP still thrives today with updates.
So I am on MDL and have OctOS 7.1.1 flashed but no root. I have tried towelroot with no success. I do however have TWRP 3.0 on my phone but SuperSU won't flash. Do you have any ideas?
Tubifex said:
So I am on MDL and have OctOS 7.1.1 flashed but no root. I have tried towelroot with no success. I do however have TWRP 3.0 on my phone but SuperSU won't flash. Do you have any ideas?
Click to expand...
Click to collapse
OctOS has root disabled by default. You have to flash a root .zip file to activate root. Make sure you are loki'ed and that you have the right TWRP version as well as the right root .zip for your phone. Towel root only works on stock Android jelly bean 4.2.2, 4.3, and kit kat 4.4.2
StoneyJSG said:
OctOS has root disabled by default. You have to flash a root .zip file to activate root. Make sure you are loki'ed and that you have the right TWRP version as well as the right root .zip for your phone. Towel root only works on stock Android jelly bean 4.2.2, 4.3, and kit kat 4.4.2
Click to expand...
Click to collapse
Where do you suggest I find root.zip file?
Tubifex said:
Where do you suggest I find root.zip file?
Click to expand...
Click to collapse
I am not too sure, I haven't messed with OctOs at all. Try here:
https://forum.xda-developers.com/galaxy-s4-att/orig-development/rom-team-octos-oct-n-t3532663
Someone there in that thread will probably know.
Finished! This guide is done!
Bump....happy flashing!
Does this APK work anymore? It will not download to my phone. I had to download it to my pc then transfer it via usb to my phone. When I go to install it I get an error saying There is a problem parsing the package.
Can anyone please provide the ATT-I337UCUAMDL-20130430103714.zip file? All the mirrors are dead
NVMD,found something similar here:
https://androidfilehost.com/?fid=23203820527944165
and here:
https://server.samsung-firmware.org...de28764422/ATT-I337UCUAMDL-20130430103714.zip
jabulon said:
Can anyone please provide the ATT-I337UCUAMDL-20130430103714.zip file? All the mirrors are dead
NVMD,found something similar here:
https://androidfilehost.com/?fid=23203820527944165
and here:
https://server.samsung-firmware.org...de28764422/ATT-I337UCUAMDL-20130430103714.zip
Click to expand...
Click to collapse
You are needing the MDL ODIN .tar / zip file correct?
7ravler said:
Does this APK work anymore? It will not download to my phone. I had to download it to my pc then transfer it via usb to my phone. When I go to install it I get an error saying There is a problem parsing the package.
Click to expand...
Click to collapse
Which APK file are you referring to? Towel root or something else?
StoneyJSG said:
You are needing the MDL ODIN .tar / zip file correct?
Click to expand...
Click to collapse
yep, but I've already found it
Thank you!
jabulon said:
yep, but I've already found it
Thank you!
Click to expand...
Click to collapse
Hi,
I'm trying to find a way to install MDL to be able to get past my att bootloader lock. I have everything except the MDL Odin file. Can you please tell me the link to get it. I'm new on the site sorry if Im in the wrong section. I want to be able to install custom rom on my SAMSUNG-SGH-I337 Att. I have already downgraded all the way to NB1 and rooted and updated all the way back to OK2 without losing Root access. I went ahead and reflashed stock for fun however to see if I could do it. It worked. So now I'm unrooted back on OK3 official via OTA. I just tricked the time on the phone, changed the date, to bypass ATT's stupid ota 24 hour update wait period inbetween updates. . So I have no issue experimenting because I have the way to downgrade all the way back to NB1 no problem with Odin and then Ota update back to OC3 then OK2, Ok3 ext. Ext. So I just need to get to MDL so I can use loki from what I have read. I'mean only able to get to NB1 basically due to lack of .tar/Odin file for the exploitable mdl bootloader.
So if I can get the Odin file or zip to MDL I will know what to do.. Thank you ahead of time for all your hard work! This post is amazing.
-Scott
(Hopefully I did this right lol)
Scottie32583 said:
Hi,
I'm trying to find a way to install MDL to be able to get past my att bootloader lock. I have everything except the MDL Odin file. Can you please tell me the link to get it. I'm new on the site sorry if Im in the wrong section. I want to be able to install custom rom on my SAMSUNG-SGH-I337 Att. I have already downgraded all the way to NB1 and rooted and updated all the way back to OK2 without losing Root access. I went ahead and reflashed stock for fun however to see if I could do it. It worked. So now I'm unrooted back on OK3 official via OTA. I just tricked the time on the phone, changed the date, to bypass ATT's stupid ota 24 hour update wait period inbetween updates. . So I have no issue experimenting because I have the way to downgrade all the way back to NB1 no problem with Odin and then Ota update back to OC3 then OK2, Ok3 ext. Ext. So I just need to get to MDL so I can use loki from what I have read. I'mean only able to get to NB1 basically due to lack of .tar/Odin file for the exploitable mdl bootloader.
So if I can get the Odin file or zip to MDL I will know what to do.. Thank you ahead of time for all your hard work! This post is amazing.
-Scott
(Hopefully I did this right lol)
Click to expand...
Click to collapse
Once your phone has been updated past MDL, you cannot go back. NB1 is the farthest back you can go without bricking. You are stuck with safe strap recovery for kit kat and flash fire for lollipop. You can only boot custom touchwiz ROMs.
Thank you so much!! You saved me a lot of time with this information. I can quit trying to find a way to go back. I will stick with flash fire and safestrap.
Scott
No problem. Be careful as safe strap works only with kit kat to my knowledge. If you're on NB1 I think that's kit kat. Flash fire works with lollipop as safe strap doesn't. Flash fire may also work under kit kat, but I am not sure.
StoneyJSG said:
Which APK file are you referring to? Towel root or something else?
Click to expand...
Click to collapse
Sorry to leave you hanging here. I was referring to towel root and I did find a good file. Thanks. I see you posted that I cannot go back to mdl after updating to OC3? Bummer! I should have researched a little more before I did that
Nope, once you update past MDL which is MK3 I believe it patches the loki doki exploit so it can't be used and also makes it so if you try to downgrade back to MDL you can brick the phone.
good guide.
err on the side of kindness