I've seen one or two threads that were in the same vein as this, but no clear resolution. Every time I open SuperSU, I get the message, "The SU binary needs to be updated. Continue?" I select "Continue," and am given the message to install it normally or through TWRP/CWM. If I try through TWRP, the phone restarts into TWRP, but does nothing. If I select "Normal," I get the "Installation failed!" message. I tried uninstalling/reinstalling SuperSU, but that didn't do anything.
In a related problem, I only have root access pretty much immediately after I reboot. Only immediately after I restart the phone can I use apps like WiFi Tether or Titanium.
I'm on stock, rooted 4.1.2. Any help would be great, thanks!
http://d-h.st/0du
Go into twrp and reflash supersu.
Sent from my HTC One using xda premium
eyeisdasteve said:
http://d-h.st/0du
Go into twrp and reflash supersu.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks for responding! Just to clarify, should I follow that readme file’s instructions, even though I’m already rooted and have TWRP? If simply choose “install” in TWRP and select this zip, will I have the option to just install SuperSU, or should I extract one of the following 3 zips in that file first?
SuperSU-v1.41.zip
superuser.zip
Superuser-3.2-RC3-arm-signed.zip
I assume this won’t wipe my phone, but of course, I’ll do a nandroid backup first.
Well, I went into TWRP, went to "install," and selected the whole .zip, but it didn't look like it was going to give me the option to flash just SuperSU.
Agh... I should do this stuff more often so I'm not so clueless each time I need to do stuff in recovery...
SOLVED!
I figured I just needed one of those SuperSU zips found in the file linked above, but first, I decided to first see if there was a more up-to-date version. I wound up downloading the updated version from here: http://forum.xda-developers.com/showthread.php?t=1538053
After flashing "UPDATE-SuperSU-v1.41.zip" in TWRP, my root access is much more robust (i.e., not losing root after one app successfully requests access) and I am no longer being prompted to update my binaries!
Thanks again!
SuperSU
subhumanderelict said:
SOLVED!
I figured I just needed one of those SuperSU zips found in the file linked above, but first, I decided to first see if there was a more up-to-date version. I wound up downloading the updated version from here: http://forum.xda-developers.com/showthread.php?t=1538053
After flashing "UPDATE-SuperSU-v1.41.zip" in TWRP, my root access is much more robust (i.e., not losing root after one app successfully requests access) and I am no longer being prompted to update my binaries!
Thanks again!
Click to expand...
Click to collapse
Glad U got it working. I on the other hand am hosed. I wish the thing worked like everything else. I consider this to be a near
fatal weakness with the product. I at this point won't update until I get a clear understanding of what the heck is up with it.
Also Kyocera does not seem to be well supported. I got a Kyocera Hydro from a family member who was going to throw it
away. Guess I should have let him
rwilcher said:
Glad U got it working. I on the other hand am hosed. I wish the thing worked like everything else. I consider this to be a near
fatal weakness with the product. I at this point won't update until I get a clear understanding of what the heck is up with it.
Also Kyocera does not seem to be well supported. I got a Kyocera Hydro from a family member who was going to throw it
away. Guess I should have let him
Click to expand...
Click to collapse
So er.. what's your problem exactly? I could try to help you out.
not updating
Hi, I'm here about SuperSU not updating, but I have a normal rom, not TWRP or thecother one. Every time I go on SuperSU, it tells me there's an update. I click continue, then Normal, because that's the rom I have, but then it says the update failed. What do I do? Please help!
limehedd21 said:
Hi, I'm here about SuperSU not updating, but I have a normal rom, not TWRP or thecother one. Every time I go on SuperSU, it tells me there's an update. I click continue, then Normal, because that's the rom I have, but then it says the update failed. What do I do? Please help!
Click to expand...
Click to collapse
TWRP is a recovery not a ROM. If Normal doesn't work, select the other one. Assuming you have a custom recovery (I recommend TWRP for this phone), it should restart into recovery and flash the update there.
Hello, im new here and if you can please answer me on German
My problem is when i start to update SuperSU Binary it is failing on Normal mode and TWRP is happening nothing.
When i rooted first everything was glad, but there was no button to update the Binary and when i used apps like Xmodgames it says, my root is maybe no succesfull, so i rooted again without deinstalling the SuperSU blabla. And now is nothing working, if i go in Root Checker it cant find my root. Pls Help, sry for bad Grammar etc.
still have the problem
I did the flashing of the latest su update zip on my recovery reboit and ny supersu still prompts me to update binary just like before...HELP!!
my samsung galaxy s duos 2 is not updating binary in any modes
what should i do please help me
Is there any other way to update the binary other than through TWRP or CWM. I can't for the life of me find a CWM or TWRP recovery for my Hannspree Titan.
Hey guys, I have a problem here...
I had rooted my tablet and installed SuperSU, I choose the normal mode for binary update but it said it failed. Then I tried in TWRP/CWM but it just restarted my tablet and there it stayed.
When I power it on, it just keeps restarting every 5-7 seconds and it doesn't do anything else.
What should I do?
Related
Ok so I have successfully rooted my phone after updating to Gingerbread. However, I had a few issues and had to read through a bunch of different posts to get there. So I'm bored and decided to consolidate everything into one.
If anyone has any other issues or fixes post them here and I will update the OP.
Credit goes to mtmichaelson and all those who helped get this working
http://androidinvasion.us/forum/index.php/topic,77.0.html
Here it is:
1. ROOT PROCESS
A. Get back to Stock:
-download the stock Zv4 ROM zip from here and put it on your external SD card- http://forum.xda-developers.com/showthread.php?t=1326893
-Back up all your apps in titanium (important: USER apps only, no data or system apps)
NOTE: It has been reported that restoring apps and data in titanium may cause some issues coming from Froyo to Gingerbread. I backed up my user apps only for easy re-install and NO data or system apps. It worked without a problem.
-MAKE SURE YOU HAVE 4G ENABLED
-boot into recovery (CWM)
-backup?
-factory reset
-select "install ZIP from SD card" in CWM, and install the stock ZIP from the link
-re-bootyour phone (you will have to re-activate it as well)
-install revo toolkit from here if it was wiped with the system reset - http://forum.xda-developers.com/showthread.php?t=1144951
-press "install recovery" and then !!!Revo Stock!!! to go back to stock recovery and wait for it to complete
B. Update to Zv6 then Zv7 (Gingerbread)
-manually search for the update and install it (this will install the v6 update)
-once that installs, manually search again to install the gingerbread update
NOTE: Some people still can't get gingerbread. Verizon has not finished rolling the update out to everyone yet.
Now here is where it gets a little dicey...
C. Rooting Your Gingerbread Phone
-pick up the rooting package from mtmichaelson here - http://forum.xda-developers.com/showthread.php?t=1326509
-follow the instructions he has on that page to obtain root
-Two issues arose for me from this point on.
2. ISSUES
A. Drivers Issue
-The first issue was that some people, including myself, couldn't download the esteem drivers.
-Some people were able to get the drivers from this page to work - http://androidnerds.net/2011/10/08/lg-esteem-oneclickroot-now-ready/.
-I was not able to get my computer to recognize my phone using the above drivers either. I would run the root command from the downloaded package and it would get stuck at "running daemon something something".
-What I did was manually uninstall the LG drivers from my computer and deleted everything "LG related"
-Then I got the drivers from the LG website at this link - http://www.lgforum.com/resources
-Scroll down to the Verizon section and download the "LG_VZW_UNITED..." drivers.
-Your phone should be recognized using the drivers from one of these links.
B. Superuser/Root access Issue - NOTE: this should be fixed now with mtmichaelson's newest root method found here - http://forum.xda-developers.com/showthread.php?t=1326509
-The second issue that came up was that the previous superuser app I had installed stayed on my phone after the updates, even though I lost root.
-The root command from the LG Esteem page would think I had root, but I actually didn't get root access.
-Apparently this issue came up on the Esteem previously and someone wrote a fix for it here - http://androidforums.com/esteem-all...-w-superuser-3-0-6-binary-3-0-3-download.html. It will uninstall the old superuser and install the new version.
3. INSTALL CWM RECOVERY
-mtmichaelson's new rooting package should automatically install CWM recovery on your phone now.
Old method:
-To get CWM back on your phone it's the same process as before the update. Get the Revo Toolkit from thecubed here and follow the instructions - http://forum.xda-developers.com/showthread.php?t=1144951
-There is sometimes an issue where the recovery does not install correctly and gives a fatal error. If this happened, make sure you have version 1.17.1 of busybox installed at system/bin. This worked for me and I got it installed correctly.
...And you should have root after trying a combination of the above. Hope this helped.
-If you have READ through this and still have any issues you can get more personalized help on the IRC channel here.
-Again I did not help with any of this, I'm just consolidating info. If you want to thank someone, thank mtmichaelson and everyone else who helped figure all this out.
-I will keep updating this as new issues arise.
Thank you for compiling this information, it is a useful reference for people to have. I know that the drivers issue took me quite a while to work out even though it is pretty simple. Hopefully this helps others to get rooted with much less trouble.
Quick question using that stock ROM will it completely unroot me?
Also a bit confused with me running revolt does that mess up me just flashing that and it has the stock boot image.
I've Revolted have you?? Sent via tapatalk plugin.
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
Hey guys, I have a new package for root for those having problems. I need testers though. If you can come on irc in about 20 minutes. It has the drivers in it also.
Sent from my VS910 4G using xda premium
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Haro912 said:
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Click to expand...
Click to collapse
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
xjli said:
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
Click to expand...
Click to collapse
Got it. I guess the first release of revo toolkit didn't have the flash stock recovery option. Can't wait to finally have gb on this thing..
Still reboots to cwm... it won't flash stock recovery. Any ideas?
xjli said:
Still reboots to cwm... it won't flash stock recovery. Any ideas?
Click to expand...
Click to collapse
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
mtmichaelson said:
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
OP updated for the new packages from mtmichaelson
xjli said:
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
Click to expand...
Click to collapse
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
jrf28 said:
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
Click to expand...
Click to collapse
Righto. Only slow 3g in my silo of an office :-/ ill let it go for a while.
Just reinstalled busybox... got it!
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
borborpa said:
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
Click to expand...
Click to collapse
It looks like it's a common problem. I haven't installed the ROM yet but mt's new gingervolt rom is supposed to make CWM stick - http://forum.xda-developers.com/showthread.php?t=1326542
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
i_t_n said:
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
Click to expand...
Click to collapse
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Haro912 said:
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Click to expand...
Click to collapse
Awesome, thank you for the quick reply. Another stupid question that i'm sure is answered somewhere on here, but what exactly will I lose when flashing a ROM, and what will I be able to restore back with a backup?
So I just recently decided to flash the unbloated OTA offered in the download section. I was on the 12 radio before running a regular ROM with ROM Manager and everything working perfectly. I flashed everything and all went smoothly. I flashed the OTA and the other required .zip. I then tried to root with IOroot25. Well my phone is detected, but when it goes to reboot into recovery, it never really does. So I tried to adb reboot recovery and the same thing happened - not going into recovery, just kinda' sitting at a very dark, though barely lit, screen.
Everything functions fine but it appears I do not have any sort of recovery at all. How would I go about fixing this? Any help would be greatly appreciated.
What debloated ROM did you flash?
BoostinBen said:
So I just recently decided to flash the unbloated OTA offered in the download section. I was on the 12 radio before running a regular ROM with ROM Manager and everything working perfectly. I flashed everything and all went smoothly. I flashed the OTA and the other required .zip. I then tried to root with IOroot25. Well my phone is detected, but when it goes to reboot into recovery, it never really does. So I tried to adb reboot recovery and the same thing happened - not going into recovery, just kinda' sitting at a very dark, though barely lit, screen.
Everything functions fine but it appears I do not have any sort of recovery at all. How would I go about fixing this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
It got removed, you need to downgrade the aboot to install a recovery once you upgrade the firmware to 24A. 24A plugs the exploit that was being used. Easiest route is to use the AutoRec app in the LG G2 Development section.
mjones73 said:
It got removed, you need to downgrade the aboot to install a recovery once you upgrade the firmware to 24A. 24A plugs the exploit that was being used. Easiest route is to use the AutoRec app in the LG G2 Development section.
Click to expand...
Click to collapse
How can I use this program if I can't attain root? It says it requires root, which IOroot25 cannot do due to not having a recovery to boot into to apply the .zip.
I'm going to try the KDZ method here to flash the factory version in its full glory. Hopefully that will restore recovery mode and allow me to root the thing. I'll report back with my findings, and whether or not I was able to do this using the above link, IOroot, and AutoRec.
I am having the same issue. I was running CM11 on a verizon lg g2 with CWM recovery. I flashed prerooted 4.4.2 from MicroMod777 along with the KK baseband. It worked, but I lost root AND recovery. Now when I tried to use ioroot 25, my phone won't boot into recovery at all. It appears that I lost recovery. Is there a simple way to install recovery back?
holsteinmoo said:
I am having the same issue. I was running CM11 on a verizon lg g2 with CWM recovery. I flashed prerooted 4.4.2 from MicroMod777 along with the KK baseband. It worked, but I lost root AND recovery. Now when I tried to use ioroot 25, my phone won't boot into recovery at all. It appears that I lost recovery. Is there a simple way to install recovery back?
Click to expand...
Click to collapse
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960
mjones73 said:
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
Yep...that did it! Thanks!
mjones73 said:
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
Running TWRP and am happy with that but would prefer CWM touch recovery. Have tried several methods to install from various XDA treads with no luck. Any info you know of on that?
CWM installed fine for me using their purchased app and just flashing the touch version after selecting my device model.
I have also installed it using .img files provided in the forums and using Flashify to flash them.
BoostinBen said:
CWM installed fine for me using their purchased app and just flashing the touch version after selecting my device model.
I have also installed it using .img files provided in the forums and using Flashify to flash them.
Click to expand...
Click to collapse
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?
holsteinmoo said:
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?
Click to expand...
Click to collapse
With 24a I pushed it with adb instead of flashing it via Flashify and it worked decently for me. Personally, though, I do like TWRP more, albeit it doesn't have that convenient application like CWM does.
holsteinmoo said:
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?
Click to expand...
Click to collapse
So you took the OTA and you're on 24A now? If thats the case you need to push the 12B aboot first before you can flash recovery. AutoRec will do all that. And flash recovery for you. After its finished you can flash CWM touch if you want.
---------- Post added at 01:13 AM ---------- Previous post was at 01:12 AM ----------
BoostinBen said:
With 24a I pushed it with adb instead of flashing it via Flashify and it worked decently for me. Personally, though, I do like TWRP more, albeit it doesn't have that convenient application like CWM does.
Click to expand...
Click to collapse
Have you ever seen this? https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager It flashes recovery for you, you can manage backups, with a donation you can even make live backups while still booted in Android. I haven't tried it yet because I keep forgetting. Sounds so cool though.
SU Binary needs to be updated on my phone - it's causing my phone to boot up, run for about 30 seconds, and then reboot over and over again.
How can I update the binary? I go to Superuser and it gives me the option to, but the phone reboots before I get the chance to update it.
I found the file I need to flash, but how can I get it onto my phone? The phone doesn't stay on long enough for me to transfer the file onto the phone...
PLEASE HELP!!
Sounds like you flashed a GSm rom that is not compatible with Sprint.
BD619 said:
Sounds like you flashed a GSm rom that is not compatible with Sprint.
Click to expand...
Click to collapse
Forgot to mention that I haven't flashed any ROM's - I rooted just so I could access mobile hotspot for free and what not.
Anyway, I actually ended up fixing it. Was able to get into SU and it posted the update file to my phone and I accessed it via recovery. Flashed it and the problem is fixed.
saj1jr said:
Forgot to mention that I haven't flashed any ROM's - I rooted just so I could access mobile hotspot for free and what not.
Anyway, I actually ended up fixing it. Was able to get into SU and it posted the update file to my phone and I accessed it via recovery. Flashed it and the problem is fixed.
Click to expand...
Click to collapse
thanks for the tip, i'm going to give this a try. something is throwing my phone into boot loops today too, I just unfroze all the stuff I froze with TB this week thinking that was the trouble.... I am on stock/rooted 4.4.2 with SU as well.
Update:
Booted to recovery, used adb to push the new Su binary (v2.00) over to phone, used custom recovery to install new su binary zip, all seems right with the world. will post again if I have troubles, but this appears to be working *crosses fingers*
I've got no idea what started this boot loop off today, maybe some OTA tweak I didn't approve? Not really sure...
bobsbobbers said:
thanks for the tip, i'm going to give this a try. something is throwing my phone into boot loops today too, I just unfroze all the stuff I froze with TB this week thinking that was the trouble.... I am on stock/rooted 4.4.2 with SU as well.
Update:
Booted to recovery, used adb to push the new Su binary (v2.00) over to phone, used custom recovery to install new su binary zip, all seems right with the world. will post again if I have troubles, but this appears to be working *crosses fingers*
I've got no idea what started this boot loop off today, maybe some OTA tweak I didn't approve? Not really sure...
Click to expand...
Click to collapse
hey man. same issue. i just tried the latest update. seems to work for now, but did the problem ever come back for you?
I just got an Ota update. I537UCUCNH3. Can't find any info online about this firmware. Anybody have any info?
does towelroot or any form of root still work?
Do not take the ota. Im capturing it right now. Once ive inspected and cleaned the updater I will post it. As far as i know it's firmware update and some updated samsung features and apps. Just hang on.
Code4U said:
Do not take the ota. Im capturing it right now. Once ive inspected and cleaned the updater I will post it. As far as i know it's firmware update and some updated samsung features and apps. Just hang on.
EDIT... It tries to patch the stock recovery/knox system/selinux setup. Im going to remove them and see what happens. Ive already cleaned the ota and made it a zip.Will report back very soon.
Click to expand...
Click to collapse
interesting. i'll wait and see what happens. i'm most importantly just trying to make sure i don't lose root.
Ive gotten it install fine but I cant stop wifi from getting forked. Im going to have to dig around some more. This happened on the first KK update because of selinux. Same is happening here also.
http://www.att.com/esupport/article.jsp?sid=KB420364&cv=820#fbid=0tcKX5Fkc73
What's changing?
Connectivity improvements related to receiving calls and text messaging
Security patch
Updated Google apps
Click to expand...
Click to collapse
Edit...Got it working perfect see post further down.
Code4U said:
I still cannot get it update and keep wifi. I took the dive and ota'd to see if its rootable. It is not,thank god for odin. Someone with more experience is going to need to look at this.Sorry guys I tried.
Click to expand...
Click to collapse
Can you post the update zip?
Yeah man do you want what I altered already, or the stock ota in zip form.
Please can you post the stock OTA zip?
Thanks
Get your upgrade here....
Here ya go OTA in original cfg. Adb push to cache/fota. Go to update and click continue. Reboot after you push, so it shows up in update section.
https://docs.google.com/file/d/0B5FxQlt9ZPF6T3k2T2o5MGJxNUE/edit?usp=docslist_api
Cfg will wipe your data,most likely will kill root and prevent re-rooting.
Here is the ota in zip form 100% stock. I just made in zip form and removed the patch checks so you can flash in safestrap.
https://drive.google.com/file/d/0B5FxQlt9ZPF6dThpek1sMHFidjA/view?usp=sharing
Flashable works fine allows you to keep root and safestrap. Here is what I did. Restore back to stock,wipe caches. Flash the zip. Mount system delete SU app from recovery file manager,leave the binary. Reboot. Check all is fine. Reboot back to recovery,flash su zip. This worked perfectly for me.
Hey guys, just letting you know if you apply the stock cfg file manually, it will wipe your data. So backup before update... I just got screwed.!!!
salwansk said:
Hey guys, just letting you know if you apply the stock cfg file manually, it will wipe your data. So backup before update... I just got screwed.!!!
Click to expand...
Click to collapse
If you need help going back to previous KK version let me know. Its really easy. Then you can use the zip to upgrade back with safestrap.
Code4U said:
Get your upgrade here....
Here ya go OTA in original cfg. Adb push to cache/fota. Go to update and click continue. Reboot after you push, so it shows up in update section.
https://docs.google.com/file/d/0B5FxQlt9ZPF6T3k2T2o5MGJxNUE/edit?usp=docslist_api
Cfg will wipe your data,most likely will kill root and prevent re-rooting.
Here is the ota in zip form 100% stock. I just made in zip form and removed the patch checks so you can flash in safestrap.
https://drive.google.com/file/d/0B5FxQlt9ZPF6dThpek1sMHFidjA/view?usp=sharing
Flashable works fine allows you to keep root and safestrap. Here is what I did. Restore back to stock,wipe caches. Flash the zip. Mount system delete SU app from recovery file manager,leave the binary. Reboot. Check all is fine. Reboot back to recovery,flash su zip. This worked perfectly for me.
Click to expand...
Click to collapse
sorry, could you be a little more specific with these? I'm still a little new. What did you do to restore back to stock? I've currently removed bloatware through titanium, so no longer have at&t software. also, i'm rooted. Am I correct in assuming this is the order?
1 - Restore to stock
2 - Wipe caches
3 - Flash the zip (The entire i537_Update.zip?)
4 - Mount system (Does this mean use the "Mount" feature in SafeStrap and navigate to the specific "System" folder?)
5 - Delete SU app from recovery file manager (completely lost as to how to do this. Is it the file manager in the "Advanced" section of SafeStrap? If so, is that only for files or can I uninstall apps?)
6 - Leave the binary (also not sure what to do here)
7 - Reboot
8 - Check everything is fine
9 - Reboot into recovery
10 - Flash su.zip (Where is this file located?)
Sorry to be a pain, just hoping to get my facts straight. Thanks.
pinyata said:
sorry, could you be a little more specific with these? I'm still a little new. What did you do to restore back to stock? I've currently removed bloatware through titanium, so no longer have at&t software. also, i'm rooted. Am I correct in assuming this is the order?
1 - Restore to stock
2 - Wipe caches
3 - Flash the zip (The entire i537_Update.zip?)
4 - Mount system (Does this mean use the "Mount" feature in SafeStrap and navigate to the specific "System" folder?)
5 - Delete SU app from recovery file manager (completely lost as to how to do this. Is it the file manager in the "Advanced" section of SafeStrap? If so, is that only for files or can I uninstall apps?)
6 - Leave the binary (also not sure what to do here)
7 - Reboot
8 - Check everything is fine
9 - Reboot into recovery
10 - Flash su.zip (Where is this file located?)
Sorry to be a pain, just hoping to get my facts straight. Thanks.
Click to expand...
Click to collapse
No problem man you got it very close. Restore back to stock,needs to be 100% stock NE3,reboot to recovery,wipe caches,install zip.Do not reboot yet,in safestrap navigate to mount,click on system, then click advanced,click file manager,navigate to where su app is(most likely in system/app) just delete it.binary is in xbin so just dont worry about it but dont delete it.Reboot.Once you see the upgrade popup,reboot recovery flash su zip and your done.I could not strip out knox or disable selinux because it screwed up wifi. theres a de-knoxing zip somewhere on here just use that after your all booted up.
Code4U said:
No problem man you got it very close. Restore back to stock,needs to be 100% stock NE3,reboot to recovery,wipe caches,install zip.Do not reboot yet,in safestrap navigate to mount,click on system, then click advanced,click file manager,navigate to where su app is(most likely in system/app) just delete it.binary is in xbin so just dont worry about it but dont delete it.Reboot.Once you see the upgrade popup,reboot recovery flash su zip and your done.I could not strip out knox or disable selinux because it screwed up wifi. theres a de-knoxing zip somewhere on here just use that after your all booted up.
Click to expand...
Click to collapse
how do you restore to stock? odin flash the NE3 files? If so, doesn't that mean I lose root, and therefore SafeStrap?
pinyata said:
how do you restore to stock? odin flash the NE3 files? If so, doesn't that mean I lose root, and therefore SafeStrap?
Click to expand...
Click to collapse
Yes flash the odin files. Dont worry about losing root just use towelroot and install safestrap again. Then flash SuperSU zip and continue. If I could make it easier I would. I spent a few hours trying to avoid all this,but there was no way around it.
If you update via OTA you will not be able to re-root using towelroot just a FYI.
I'll stay on MF3 its not big changes... I'm waiting for kitkat 4.4.4
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Root
So the only way to root is flashing an older kernel and root with towelroot and flash the newer kernel again?
That is at least what I see for other phones that have gotten updates that broke towelroot.
Hey, my friends of the L90 Discussion Forums.
I know there was already a previously made text guide for this, but since some people like visuals, I made a quick video tutorial for it.
All the instructions and download links are in the description of the video. I'll paste them here just if you are too lazy to get the YouTube video open from the YouTube site.
Here's the video:
(Sorry for any wording mess-ups I made. I'm a better script/speech writer than I am a presenter.)
https://www.youtube.com/watch?v=vaGM-TtlRbM
__
I did not originally come up with how to get the bootloader. Credit to Quarx from XDA and his friends at 4pda.ru.
Ok, So, here are the instructions if you did not find it clear enough from the video, and got your **** stuck in a ceiling fan:
Requirements:
1. Root (Use Towelroot)
2. Terminal app (I used an app called Android Tuner Pro. Remember to enable SU when installing Recovery and rebooting or it may not work)
3. twrp.img - http://bit.ly/1IZ2BRn - download from google drive
Instructions:
1. Ensure that your phone is rooted.
2. Download and move twrp.img to internal sdcard (/sdcard)
3. Open up terminal app, ENSURE THAT YOU HAVE SU ENABLED, and type in this command:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
3.5. If the command works, it should take a few seconds and it will say "11 MB has been transferred in so and so seconds"
4. After that, type in:
reboot recovery
It should then reboot into the newly installed TWRP recovery. Wait now, Why isn't anything working when I touch it? Well, TWRP has a small error that doesn't recognize touches the first time around, so wait till the screen times out after 60 seconds, turn the screen back on, and unlock. Then it should be usable. Remember to change the screen timeout to 15 if you don't want to wait.
There you go, that should be about it.
Enjoy!
Disclaimer: I do not take responsibility for damage done to your phone. You do this at your own risk.
See original instructions here: (go down to quarx's post) http://forum.xda-developers.com/showthread.php?t=2770938&page=31
__
That's a good video. Thanks for taking the time out to make it. Do you know where I can find towelroot? I tried www.towelroot.com, but it said that there were problems with the security certificate. I can't find it in the play store either.
EpicSaga said:
That's a good video. Thanks for taking the time out to make it. Do you know where I can find towelroot? I tried www.towelroot.com, but it said that there were problems with the security certificate. I can't find it in the play store either.
Click to expand...
Click to collapse
APK Attached.
I just installed TWRP on my LG D415, thank you.
EpicSaga said:
I just installed TWRP on my LG D415, thank you.
Click to expand...
Click to collapse
Oh, you're welcome! Hope you enjoy it!
Can I flash CM11 using TWRP after installing TWRP using this method, ? Is there a way to access TWRP Recovery by pressing a combination of buttons when the phone is rebooting? I tried to load TWRP Recovery by turning off the phone then pressing the volume down button and the power button, but I got the factory hard reset instead. I didn't do the factory data reset.
EpicSaga said:
Can I flash CM11 using TWRP after installing TWRP using this method, ? Is there a way to access TWRP Recovery by pressing a combination of buttons when the phone is rebooting? I tried to load TWRP Recovery by turning off the phone then pressing the volume down button and the power button, but I got the factory hard reset instead. I didn't do the factory data reset.
Click to expand...
Click to collapse
I have not tried flashing any ROMs or anything yet on it.
Also, I found a key combination, which is exactly the one you said. Problem is, the guide I read it from said you need to go through with the Erase Phone and whatever, and then it will load your recovery, but I'm not risking what I've done so far just to try to get into Recovery.
Instead, I made a small app that uses the Shell and Root to simply perform a reboot into Recovery by the press of a button.
Attached.
(916 KB compressed, 3.01 MB when installed)
WARNING: 4.0.3+ (API 15+)
Sadcamp said:
I have not tried flashing any ROMs or anything yet on it.
Also, I found a key combination, which is exactly the one you said. Problem is, the guide I read it from said you need to go through with the Erase Phone and whatever, and then it will load your recovery, but I'm not risking what I've done so far just to try to get into Recovery.
Instead, I made a small app that uses the Shell and Root to simply perform a reboot into Recovery by the press of a button.
Attached.
(916 KB compressed, 3.01 MB when installed)
WARNING: 4.0.3+ (API 15+)
Click to expand...
Click to collapse
I followed a video on youtube on how to flash recovery for the LG 3. I did the combination of volume down and power button and selected the factory data reset and it loaded TWRP. It looked like the stock factory data reset prompts until it loaded TWRP. It didn't erase anything. What does the .apk do that you posted?
EpicSaga said:
I followed a video on youtube on how to flash recovery for the LG 3. I did the combination of volume down and power button and selected the factory data reset and it loaded TWRP. It looked like the stock factory data reset prompts until it loaded TWRP. It didn't erase anything. What does the .apk do that you posted?
Click to expand...
Click to collapse
There's just a button in the middle of the screen that says "Boot into Recovery".
It requests Superuser so that it can run the shell command "reboot recovery".
Screenshots attached. (Also, uploaded it to the Play Store, will be up in a few hours)
Sadcamp said:
There's just a button in the middle of the screen that says "Boot into Recovery".
It requests Superuser so that it can run the shell command "reboot recovery".
Screenshots attached. (Also, uploaded it to the Play Store, will be up in a few hours)
Click to expand...
Click to collapse
Which Superuser app is the best? I am using is from ChainsDD, it might be outdated though. Are you using chainfire's Superuser App? After looking at the screenshots that you posted, and I looked on the playstore and that was the only one that looked similar. Merry Christmas
EpicSaga said:
Which Superuser app is the best? I am using is from ChainsDD, it might be outdated though. Are you using chainfire's Superuser App? After looking at the screenshots that you posted, and I looked on the playstore and that was the only one that looked similar. Merry Christmas
Click to expand...
Click to collapse
I believe I am using Chainfire's.
Merry Christmas to you too.
Sadcamp said:
I believe I am using Chainfire's.
Merry Christmas to you too.
Click to expand...
Click to collapse
Is it possible to switch to another Superuser app? I don't think I saw any support for this Superuser app from ChainsDD when I installed it. The only thing that interests me is that it has OTA Survival. I guess that means it will survive an OTA update.
EpicSaga said:
Is it possible to switch to another Superuser app? I don't think I saw any support for this Superuser app from ChainsDD when I installed it. The only thing that interests me is that it has OTA Survival. I guess that means it will survive an OTA update.
Click to expand...
Click to collapse
Yeah, I do believe there should be, mostly, ability to switch root apps.
Is it safe to flash CM11 once you have recovery? Would that take erase towel root and root access somehow and then TWRP along with it? Or would TWRP recovery survive?
I am unsure. I am the kind of guy that enjoys Stock so I've never bothered to flash anything. Best off asking someone who is a heavy flasher and active user.
Sent from my LG-P769 using XDA Free mobile app
EpicSaga said:
Is it safe to flash CM11 once you have recovery? Would that take erase towel root and root access somehow and then TWRP along with it? Or would TWRP recovery survive?
Click to expand...
Click to collapse
Towel root is only used for the rooting process, it can be deleted once you install supersu and busybox, or like you want flash a custom rom, any thing is safe oto do once you have a custom recovery as long as you follow op's directions on flashing their rom. Always read directions and as much info as can first. Recovery will always be safe unless you flash a kdz with lg flash tool which is used to completely return to stock, recovery, system and all. Also always back up while in recovery before flashing. Its always good to have back up stock rom, or any roms you like in case you decide to switch back or between them.
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Towel root is only used for the rooting process, it can be deleted once you install supersu and busybox, or like you want flash a custom rom, any thing is safe oto do once you have a custom recovery as long as you follow op's directions on flashing their rom. Always read directions and as much info as can first. Recovery will always be safe unless you flash a kdz with lg flash tool which is used to completely return to stock, recovery, system and all. Also always back up while in recovery before flashing. Its always good to have back up stock rom, or any roms you like in case you decide to switch back or between them.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
What does busybox do? I installed it and every time I open the app it says "Smart Install is loading ...You may go ahead and install Busybox or wait for Smart Install to finish loading". There are boxes to tick under "Smart Install" that can only be used in the PRO edition. The boxes are: "Enable Smart Install", "Replace All (Symlinks all)", and "Clean Mode". I don't know what these options do, but from the reviews I've read the PRO edition can break WIFI and even break the phone. If I do buy the PRO edition, and I flash CM11, it would wipe out the app. Would I have to buy it all over again from the play store?
EpicSaga said:
What does busybox do? I installed it and every time I open the app it says "Smart Install is loading ...You may go ahead and install Busybox or wait for Smart Install to finish loading". There are boxes to tick under "Smart Install" that can only be used in the PRO edition. The boxes are: "Enable Smart Install", "Replace All (Symlinks all)", and "Clean Mode". I don't know what these options do, but from the reviews I've read the PRO edition can break WIFI and even break the phone.
Click to expand...
Click to collapse
Just open the app and click install once rooted and supersu binarys are install. Rooted apps use the commands and things busy box installs to run. Never had an issue with it, like said just hit install and leave the app on the phone for updates. When you install a custom rom they're s already built in, really only use for rooting the stock rom.
Sent from my LG-D415 using XDA Free mobile app
aerdely said:
Just open the app and click install once rooted and supersu binarys are install. Rooted apps use the commands and things busy box installs to run. Never had an issue with it, like said just hit install and leave the app on the phone for updates. When you install a custom rom they're s already built in, really only use for rooting the stock rom.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
What is the Applet Manager?
EpicSaga said:
What is the Applet Manager?
Click to expand...
Click to collapse
Never used it, also to tell you the truth im not rooted st the moment, i went to stock to tske the 10e update and there no method as of now to root it, i could go back to 10c but i found that the update was improved on handling ram, that was the only reason i used a custom rom for a while. Once thetes a root method i may go back.
Sent from my LG-D415 using XDA Free mobile app