Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
OCTAF1SH said:
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
Click to expand...
Click to collapse
It sounds like CWM hasn't reflected TWRP, have you tried using the tool kit again just to flash CWM? Or how about flashing CWM via Odin using the recovery in the below thread?
http://forum.xda-developers.com/showthread.php?t=2232856
Sent from my Nexus 7 using xda app-developers app
OCTAF1SH said:
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
Click to expand...
Click to collapse
I think when you rebooted into system in CWM, you accidentally chose to revert to the old recovery
Thanks so much for the answers guys. I went ahead and flashed a rom anyway, figuri g that as long as A recovery was in place, it would be ok, and it seems to be so.
And it turns out I am happy with TWRP and as the old sayi g goes, if it aint broke....
I only chose CWM as the previous root had failed, so I tried with different variables, ot because of a burning preference for one over the other.
Thanks again for your help.
Wil.
Related
I am a noob.
I followed some instructions to prepare my N1 for the OTA 2.3.3 update and messed some things up. I cleared EVERYTHING from Clokwork recovery, but, then phone would not boot anymore. So I manually loaded a Cyan 6.1 and GApps zip and got the phoen to load. Finally ran clockwork, rom manager, backed it up. Then I downloaded the stock image FR91 from ROM manager, clear cache/data and rebooted. Phone updated from 2.2 to 2.2.2. Now I have all my apps back and stock ROM, but superuser will not work. I cannot flash clockwork now, and cannot use ROm manager. Titanium prompted me to update superuser binary thru a zip file, but it will not run. Now, I tried to access recovery thru bootloader, but it just give me the Android with the ! and nothing more.
Alos, ROM manager keeps saying my phoen is not rooted, but when I bought it (used) it had Cyanogen 6.1. I know it's rooted, I get the unlocked boot screen, but why the problems now? How can I regain superuser functions to use ROm manager again?
Thanks in advance.
This is what happens when people don't read and don't understand what they're doing.
ROOT is a user in OPERATING SYSTEM = Android OS.
LOCK is a property of BOOTLOADER = a program that boots the phone.
Stock = NOT ROOTED, until you root it.
UNLOCKED = allows you to flash ROMs and other partitions directly from bootloader.
The 2 have no relation whatsoever, besides one - being UNLOCKED makes it easier to gain ROOT.
This has been discussed here a zillion of times. Do yourself and XDA a favor, please, and invest some time in reading Wiki - it points to several 101's (things to know) and guides.
So in my case I have unrooted the phone and should research on how to root again?
Thanks for the reply. I suppose I just confused myself.
So if I root again this will/will not affect the OTA update?
Sent from my Nexus One using XDA App
Wiki contains rooting guide.
Rooting won't affect OTA.
Custom recovery will affect OTA, unless signature checking is turned off in it.
You will have to root it.
A stock rooted rom will get the OTA. It will update as long as you don't remove stuff from stock. Like Amazon, twitter.
Please read the wiki.
Sent from my Nexus One using XDA App
Hello everyone.
I got a little problem with my phone, since i want to root it, i checked out which build I had installed on my phone, here's the results:
i.imgur.com/1sOmg7i.png
As you can see, my build is an AMG3/AMF3, and i couldn't find any guide for rooting with that build installed.
What should i do?
Thank you in advance,
Amaryl.
Hi there,
Firstly, I am new to all this too, so take my advice, or leave it, with that in mind!!
I have recently rooted mine from the AMG3 build with mskip's toolkit. I took the plunge and took his advice on choosing the closest available build. I donated so as to be sure I had his latest update of the toolkit. I am not near my pc, but it was the selection which included the AMD3 build (the most recent, ie bottom in the section for the model with NFC, as that is themodel I have). I had one root through odin which failed to give superSU any binaries or permissions at all, so then completely reinstalled the toolkit on my pc (possibly unnecessary) and then reflashed twrp recovery, but chose the cwm version of superuser and ot worked perfectly! As far as I can tell, my phone works exactly as it did before, but now with root access.
If you look in this section of the forum, I posted a q this morning which gives a couple more details about the process I went through re 1st failed attempt which I won't retype here, but I can confirm I have full rooted functionality with the toolkit over the AMG3 build on the N model of the mini, with twrp and superuser!
Btw I say a failed attempt, but my phone worked fine, I just got an error message at the end of the toolkit installing busybox, so booted the phone and superSU just said "there are no binaries I stalled, this is a problem!". So I assume I wouldn't have been able to exploit the root, but at no point did It stop the phone working as a phone.
As I say, I am faaaar from an expert, but that's my experience.
Hi, first of all, sorry if my english is wrong sometimes, I am French.
I was on CM11 M12 and wanted to update to CM12. It could not flash and I tried to wipe again before reflashing but my error was to wipe the system I think. From then, no OS. I followed many threads, tried to flash others ROMs, even RUU by all means (sideload, fastboot..) But my phone seemed not to accept any of them.
FInally, yesterday after 5 days of struggle, I managed to flash the Omnirom. I can't explain why this one worked but well it did. Now the problem still is it always fails when trying to flash gapps or trying to root. It is like my phone can only flash some specific stuff. At least, my phone is working right now, and I have no network problems. But yeah , can't flash gapps or root.
I tried to root with towelroot but not working either. If I could get root access, I was told (on a french forum) that I would be able to copy paste the gapps stuff right where it has to be in the system.
I never had such issues before, I could flash any ROM, root easily. If someone could explain
Thanks for helping
Little update.
I finally got it to work. I used Root Genius to root my phone. I copied/pasted the gapps in /system/app and /system/priv-app with Root Explorer. Then reboot and all was good.
Hey guys,
Followed a guide (which I cannot post a link to because I'm too new to the forum) today and I get a message that says "Your device is corrupt. It cannot be trusted to work properly". After this message, it won't boot. At all. I had the latest version of Marshmallow when I attempted this. Never rooted before. New to this whole scene. Hoping for some guidance on how to fix this.
I tried wiping with the TWRP installed and rebooting, but I get the same message. I can still plug in to my Mac and use Android File Transfer.
Thanks!
guide: on androidrootz /2014/12/how-to-root-nexus-6-windowsmaclinuxubun.html
EDIT: Just needed newest supersu. Works fine now. Don't follow old guides, and make sure you have the newest software =]
You are not hard bricked, you will get out of this.
Sounds like you flashed the old root. You must use 2.60 or higher. 2.66 is current.
Flash it back to stock.
Flash twrp.
Copy over root 2.66 from Chainfire and install it with twrp.
When you exit twrp it will ask you if you want to root your phone. NO. Always answer no to that question from twrp.
The old way modifies the system. The new android does not like that.
And, just looking at your link, that guide is over a year old. Always try to look for fresh information. A lot happens to change things during a year...
TonikJDK said:
You are not hard bricked, you will get out of this.
Sounds like you flashed the old root. You must use 2.60 or higher. 2.66 is current.
Flash it back to stock.
Flash twrp.
Copy over root 2.66 from Chainfire and install it with twrp.
When you exit twrp it will ask you if you want to root your phone. NO. Always answer no to that question from twrp.
The old way modifies the system. The new android does not like that.
Click to expand...
Click to collapse
Resolved the issue. Got it. Thank you!!! Just needed to install the newest root (2.66)
Hi,
I made this guide after struggling to install TWRP using several guides on XDA and other forums which fail to mention few other steps needed.
I am using a verizon lg g2 on stock lollipop 5.0.2 , rooted using LG ONE CLICK ROOT. But i guess this guide goes for all g2 variants who cannot simply install twrp on their stock firmware using flashify or autorec.
ISSUE :
I have tried flashify but this app is only useful if you already have an older version of recovery installed since i failed to install any version of twrp and cwm while trying. After installing a twrp , you can flash upgrade recovery using this.
Autorec gives me unresponsive button when tapping on the FLASH TWRP icon.
Other solution requires manual installation such as THIS GUIDE which i haven't tried because i am not that advanced android user yet since i came from using iOS.
The easiest way to install TWRP is autorec but to fix the unresponsive button, follow below steps:
** Ofcourse you need root in order to install custom recovery
1. Install AUTOREC from HERE. There are different app for different g2 variant so install accordingly.
2. Go to SuperSU settings , uncheck " Enable Superuser" and then scroll bottom where you see " reinstall" under CLEANUP section. Tap on that and proceed. Wait few seconds and when done, reboot your device.
3. Go to THIS LINK and download supersu 2.46
4. After its downloaded, tap and install it. Update binary and reboot.
5. Go to autorec, give it superuser permission and tap on the "Flash TWRP" icon and you will see it working.
** note : in order to install latest twrp, you must first install the initial img version and then flash the latest version zip from within. Update link : TWRP 3.0.2-1
Feel free to post below if it worked for you or if you need further assistance.
Help with twrp & flashing rom on g2
I have a rooted G2, ATT W/stock KitKat. At one point when I bought it, it had Lollipop, and TWRP, but I bricked it trying to install Magisk as a workaround to play Pokemon. That began my unwanted journey into the world of rooting, custom recovery, flashing, and the whole bit. I've watched many videos and read many threads but I'm very much a "noob" , and something always goes wrong. I can, and do read instructions but, I have found that usually I don't understand all the slang techy terms, and/or important steps are left out of the tutorials. Most recently, I tried to install TWRP using AutoRec and a YouTube video, and got stuck in TWRP and "soft-bricked".
I started a thread on here asking for help, even offering to donate, and got like 2 short replies saying "flash a custom ROM". Like that explains anything to a newbie.... When I clearly state I'm new at this, that doesn't help. Then today I get notification my thread was moved. Anyway, for a third time, I had to (follow the only YouTube tutorial that has actually worked for me), which just unroots, and puts the device back to a damn factory reset state.
MY GOAL is that I'm bound and determined to at least get Lolliop back on the device. I prefer that over KitKat. I also would love to be able to play Pokemon again, since the a**holes at Niantic blocked rooted phones from playing. Even after I did the factory restore thing and unrooted, the game still wouldn't install, saying "device not compatible". Apparently the Magisk workaround works for some people...
I am getting so frustrated and should just leave well enough alone. Everytime I say I'm not going to mess with it anymore, I end up trying, against my better judgement, and end up bricking.
So one last try.... - If there is anyone out there in XDA land with the ability, or inclination to help, I would greatly appreciate it. I'm not a simpleton, but apparently there are so many things that have to be done precisely, or I get bricked.
If anyone can give simple, step-by-step instructions, leaving nothing out, accounting for anything that might go wrong, provide links that still exist, etc, etc. I will not only be a very happy guy, but my daughter will be happy that she can play Pokemon again, and I will be happy to have Lolliop, or even, dare I dream Marshmallow, and I would GLADLY donate a few bucks to whatever account...
If you've read this far, thanks for that, at least.
it works , thanks man ?
note : I used kingroot to rooting my device .
No dice on AutoRec... do I need a special version?
AutoRec doesn't seem to actually do anything and flashing the recovery through any of the normal programs just leads to an error message when trying to enter recovery. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!
Bill720 said:
AutoRec doesn't seem to actually do anything and flashing the recovery through any of the normal programs just leads to an error message when trying to enter recovery. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!
Click to expand...
Click to collapse
Can you please explain that in nubbie terms like step by step i would greatly appreciate it thank you in advance
Clarification
jboo01 said:
Can you please explain that in nubbie terms like step by step i would greatly appreciate it thank you in advance
Click to expand...
Click to collapse
To get the AutoRec app to work, you need to uncheck "tapjacking protection" inside of the SuperSu app (or its equivalent in whatever root manager you use).
not work in d805 lolipop ??????