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)
Related
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.
Hello
I've just don't an OTA upgrade to Android 4.3 to my new Sprint HTC One.
After the OTA I rooted the device and installed recovery.
After I restarted the phone and launch the SuperSU I got this message :
"There is no SU binary installed, and SuperSU cannot install it. This is a problem.
If you just upgraded to Android 4.3 you need to manually re-root."
I would like to ask what should I do to make the root process sucseful .
I'm a newbe in the Android world and use some root manual I found.
1. What does it mean to re-root?
2. Should I unroot first ? And how it can be done?
3. Is there an 4.3 root manual somewhere to the make the SuperSU work?
Any instructions will be great help.
Thanks
Did you ever figure out how to get root? I am currently experiencing same issue.
Same issue
Same exact problem! Bump.
Any suggestions?
Please don't take OTAs after you've rooted your phone, because almost always it will wipe your root. Here is how I do my rooting.
Step 1: Go to htcdev.com and get your bootloader unlocked (this process will reset your phone back to factory setting, so back up all your pics, music, etc)
Step 2: Right after bootloader is unlocked, install a custom recovery (I prefer TWRP 2.6.3.0 for Sprint HTC One 4.3)
Step 3: As part of TWRP installation, SuperUser will be installed (root)
Step 4: Make a nandroid backup of your phone in TWRP. After that, install a custom ROM of your liking (there are plenty wonderful ones in Development section). This will keep your phone from taking OTA updates from Sprint/HTC. Don't worry, Devs on these forums (and their respective ROMs) are months ahead of Sprint in terms of updates.
For more details, head over to Development section and look for rooting instructions. there are very detailed tutorials there. Hope this helps.
having the same problem! im getting "There is no SU binary installed, and SuperSU cannot install it." from super su! I DO NOT WANT A CUSTOM ROM! i want stock rom but i want to have root. please help! the theres so many devs here im sure someone is kind enough to help
`Ghost` said:
having the same problem! im getting "There is no SU binary installed, and SuperSU cannot install it." from super su! I DO NOT WANT A CUSTOM ROM! i want stock rom but i want to have root. please help! the theres so many devs here im sure someone is kind enough to help
Click to expand...
Click to collapse
If all you want is pure stock with root -- just flash one of the already rooted stock ROMs in your custom recovery (assuming you loaded TRWP or PhilZ or CWM):
http://forum.xda-developers.com/showpost.php?p=48653344&postcount=2
If you want (more or less) stock with a *significantly* better experience (e.g., 30 volume steps, extreme stability, bla bla bla), I'd suggest InsertCoin (the thread is here whereas the download for our phone is here.
For either pick, since your coming in fresh to the ROM, do a full wipe (InsertCoin will do that for you as an option to the install, but I usually do that in recovery anyway).
Also -- note that InsertCoin *might* start the install and seemingly hang. That's a bug in Aroma, just hard restart the phone and try again -- letting the installer perform the wipe. It will work, and you'll be happy -- I'm sure.
---------- Post added at 05:03 PM ---------- Previous post was at 04:22 PM ----------
james341 said:
Hello
I've just don't an OTA upgrade to Android 4.3 to my new Sprint HTC One.
After the OTA I rooted the device and installed recovery.
After I restarted the phone and launch the SuperSU I got this message :
"There is no SU binary installed, and SuperSU cannot install it. This is a problem.
If you just upgraded to Android 4.3 you need to manually re-root."
I would like to ask what should I do to make the root process sucseful .
I'm a newbe in the Android world and use some root manual I found.
1. What does it mean to re-root?
2. Should I unroot first ? And how it can be done?
3. Is there an 4.3 root manual somewhere to the make the SuperSU work?
Any instructions will be great help.
Thanks
Click to expand...
Click to collapse
See my previous post (you can just load a rooted stock ROM). But "re-root" is something you do by either flashing the SuperSU.zip file, or letting your recovery take care of re-rooting.
No need to unroot.
My take? Backup your current ROM (stock, unrooted) and then flash one of those I mentioned.
This might be of some help, or at least clarify the issue you are having.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
fyi i realized i was flashing with an older version of supersu. V1.25 to be exact. I slapped supersu v1.86 on my phone and then installed that through TWRP. Root was successful.
Reason for rooting was I wanted to install titanium backup and freeze sprint id and other bloatware apps. I also wanted to eliminate GPU throttling which i did, and I set up the scrips to stop CPU and GPU throttling while im playing games, and then click the other button to shut off the script. Im happy with its performance. Shadowgun and modern combat 4 run much more smooth since doing that.
as for a custom rom im not sure im that brave yet... i thought all the big hubbub was cyanogen. has that mod lost its step? ill look in to the one you suggested, thanks.
after looking at insertcoin im going to have to pass. Ive read that kitkat completely breaks the phone for gaming and performance becomes horribad
[Q] Having trouble figuring out rooting & recovery works on Moto X coming from Nexus
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
mateopase said:
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
Click to expand...
Click to collapse
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
IINexusII said:
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
Click to expand...
Click to collapse
Awesome, thanks. Looks like that's what I'll end up doing. I really messed up my phone though when trying to get back to stock. Hopefully my stock image request will be approved soon and I'll be able to go through the process again.
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
mateopase said:
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
Click to expand...
Click to collapse
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
crpalmer said:
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
Click to expand...
Click to collapse
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
mateopase said:
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
Click to expand...
Click to collapse
Honestly, I haven't looked at what options are available for images to flash.
When I asked for firmware, I believe that I asked on a Friday evening and received access on the following Monday morning. So maybe you'll get access in another 15-16 hours? That is your safest bet if your phone is working well enough to last you until then.
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 ??????
Hi there,
after some attemps I succesfully rooted my fire7. More than one time it happend, that my modding and flashing attemps lead into a bootloop. There was no choice than sideloading 5.3.1 Firmware and going through the whole rooting process again. (Annoying)
In the End I decided to stay with a rooted FireOs since it was the only Rom where screenmirroring worked flawlessly. Now I was wandering if there was a way to create a prerooted and modded backup img, that I can safely sideload. I think it could be possible since I'm still on the 'original' rom whixh I initially sideloaded.
snoerme said:
Hi there,
after some attemps I succesfully rooted my fire7. More than one time it happend, that my modding and flashing attemps lead into a bootloop. There was no choice than sideloading 5.3.1 Firmware and going through the whole rooting process again. (Annoying)
In the End I decided to stay with a rooted FireOs since it was the only Rom where screenmirroring worked flawlessly. Now I was wandering if there was a way to create a prerooted and modded backup img, that I can safely sideload. I think it could be possible since I'm still on the 'original' rom whixh I initially sideloaded.
Click to expand...
Click to collapse
No ready-made tools as most require access to a custom recovery (eg: TWRP) for assured recovery. Next best option is the backup/recovery capability built into FlashFire. Note this requires a bootable/functional/rooted/stable ROM to pull off a comprehensive recovery. More of a checkpoint than full restore.
so it's not possible to sideload the backupfile that flashfire created?
It's kind of annoying to go through the kingroot procedure again and again.
snoerme said:
so it's not possible to sideload the backupfile that flashfire created?
It's kind of annoying to go through the kingroot procedure again and again.
Click to expand...
Click to collapse
Correct and agree. Lucky we can do anything with this device given bootloader state.