I was using Visionary to temproot my Shift. I am halfway through the permanent root process (step 6), but Visionary no longer lets me temproot. I read in another thread about issues with superuser and temprooting a second time, so I uninstalled superuser. That didn't fix my problem.
When I try to temproot now, the process starts, runs for 8 seconds, then the phone reboots.
Visionary is not set to temproot at boot. If I try unrooting, Visionary tells me the phone isn't rooted.
One thing which is unusual is that the phone continues to reboot after Visionary fails the temproot. Sense begins to load, then the phone reboots, and it will continue to do this unless I pull the battery.
Ideas or suggestions for completing permroot are greatly appreciated.
You need to uninstall visionary and do a reboot.
powered by the tears of a million orphaned alpacas...
Also, make sure you have airplane mode enabled. I think that is in the instructions though.
Sent from my PG06100 using XDA App
OK, uninstalled Visionary, powered down, pulled the battery, booted, and verified that Visionary was not installed. I then installed it, tried the temproot, and the phone rebooted.
This is crazy....
This is a common issue among alot of us shift users, youll also notice on the reboot on a failed temp root that the phone is superbly slow, etc, try powering down on a failed temp root normally (meaning dont pull the battery actually power it down) wait a few, then power it on. Let it boot, and wait a few seconds after getting into the home screen, one it seems to have fully loaded everything, go ahead and attempt a temp root with visionary, if you are successful continue on with the perma root instructions. I had the same issue,however just so you know I had to make sure that my phone was NOT in airplane mode for the temp root but it needed to be in airplane mode for the Perma root portion, if i tried it any other way it failed, but now i have a perma rooted shift and it works perfectly. Hope that helps.
Yes, I have airplane mode enabled. I have followed the permroot instructions to the letter.
Very frustrating........
RESOLVED
I had to reset the phone to factory defaults, install Visionary, and proceed from that point.
Thankfully I had backed everything up with Titanium Backup before starting the entire process.
Thanks to all who gave suggestions and advice.
Related
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899
Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App
Also, you need to flash CW at least twice for it to take.
CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.
lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
First thing's first. Pull the battery for about a minute. Reinstall it then plug in the phone but don't try to boot. If the orange light comes on that's good. If not you might be in trouble but all hope is not lost yet.
krohnjw said:
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899
Click to expand...
Click to collapse
This is your best bet. Re-image it completely and start over, this time READ THE ENTIRE TUTORIAL BEFORE TOUCHING IT!!
jjjackson56 said:
Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ADB probably won't be much help since he's not perm-rooted; it won't let him do anything. Just re-image the sucker.
CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
In order to perform a nandroid backup you need:
1. Perm root, NOT temp root, PERM ROOT.
2. S-OFF so you can successfully flash clockwork recovery.
Not trying to be harsh just want to be perfectly clear.
TeeJay3800 said:
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.
Click to expand...
Click to collapse
Yup.
Ok, so I'm trying to root my phone via the guide, however I'm hitting a major snag.
and this happens with either visionary or z4root. whenever i run them to temp root to start off with the instructions, they either cause the phone to completely reboot and then it is painfully slow. like so slow that i swipe the screen to goto another home screen and have to wait for it to catch up. end with me having to pull the battery and starting over. this has happened several times in a row and is starting to make my head hurt from the frustration.
now, if either app comes back with the "you are now temporarily rooted" success screen and i hit the home button. it seems i still don't have root. for example, if i run z4root and hit the temp root button. it'll do its thing. give me the success screen. i hit home. but if i go back into the z4root, it says "temp root" or "perm root" again. not "reroot" like it should. also checked with titanium backup and it says i do not have root access despite z4root just saying it was successful. Same thing happens with visionary as well.
so i'm stuck. what is going on that is keeping it from temp rooting? i'd like to be able to perm root the thing and be done with it.
also doesnt help that with every boot i have to sit through that long as hell 4g boot screen. why is that so long?
still trying to figure this out. tried rooting while in airplane mode, didnt work. tried doing a normal reboot twice in a row without trying to root in order to get as clean of a boot as possible. figured a reboot from an already normally booted phone was as good as it was going to get. still, the temp root either resets the phone where it becomes slower than a snail in ice. or it "says" it's temp rooted but yet any app that needs root says "unable to obtain root access" or "this will only work on a rooted phone". ugh.
When I temp rooted with Visionary and tried to load Titanium, I couldn't either. I clicked problems and downloaded busybox. Seemed to work after that.
that sort of worked. The first time it didn't do anything. kept saying no root access. so i hit the "unroot" button in vinsionary and let it reboot and then tried temp rooting again and it worked after i did the "problems?" option. So thanks for that tip. gonna leave my phone rooted like this till i get home where i can perm root it.
Uninstall Z4, Visionary, and Superuser
Reboot
Reinstall Visionary
Run temproot
Verify Superuser is present
open Titanium Backup and if you still are having issues click on the problems button as previously selected
got it working! and now I'm permanently rooted. thank you all!!
viperv303 said:
got it working! and now I'm permanently rooted. thank you all!!
Click to expand...
Click to collapse
Awesome! Congrats
I successfully used the gfree method and set s=off, updated my bootloader to .85.2007 using the great guide here:
http://forum.xda-developers.com/showthread.php?t=858996
The problem is getting permroot to work. Using visionary, I can temproot without any problems and su on a terminal, use rom manager, root-explorer. Everything. But when trying to use Visionary to permroot, it just acts like I am not doing anything. The button just clicks and sits there. It lets me click it again, but it never leaves the menu.
Its not the worst problem in the world, but it would be nice not to use visionary after every restart.
lockback said:
I successfully used the gfree method and set s=off, updated my bootloader to .85.2007 using the great guide here:
http://forum.xda-developers.com/showthread.php?t=858996
The problem is getting permroot to work. Using visionary, I can temproot without any problems and su on a terminal, use rom manager, root-explorer. Everything. But when trying to use Visionary to permroot, it just acts like I am not doing anything. The button just clicks and sits there. It lets me click it again, but it never leaves the menu.
Its not the worst problem in the world, but it would be nice not to use visionary after every restart.
Click to expand...
Click to collapse
if you have temp rooted w/ s=off you do not need to permaroot. The Security Protocol is going to remove any SU access. So you are good to go.
do this, turn off the phone. and pull the battery. put it back it and turn on the phone go to Term Emulator and type "su". do not even worry about the VISIONary program. if the $ changes to a # you are good to go.
Thanks for the response.
I have s=off (just confirmed), and when I do exactly as you said I get a "permission denied" message after running SU. I can't change mount in root explorer either. I would need to run visionary again and temp root to get root access again....
lockback said:
Thanks for the response.
I have s=off (just confirmed), and when I do exactly as you said I get a "permission denied" message after running SU. I can't change mount in root explorer either. I would need to run visionary again and temp root to get root access again....
Click to expand...
Click to collapse
Try this.
uninstall Visionary, reboot the phone to clear up any unwanted cache, and reboot into bootloader and clean the cache and the Dalvik cache then re download VISIONary direct from the site via a computer with a Landline connection, or strong wi-fi connection then push the visionary.apk via a USB cable and install it that way.
just to make sure you do not have a faulty visionary program.
I had the same problem, on three phones. I did get it to run one time after uninstalling, rebooting and installing again.
I didn't plan on staying stock though, so I didn't need to run permroot. I just ran temp root with r/w access to system then downloaded ROM manager from the market and used it to flash clockwork recovery. (it defaults to flashing 3.0, but if you want to use Iced Glacier ROM flash clockwork 2.5.1.2) After that I just rebooted into recovery and nandroid'ed my stock ROM then flashed a new one. Iced Glacier is practically stock, so try it first.
A good idea on clearing everything, sadly, same behavior. Temp root works fine, permroot just ignores the fact I hit the button, and reboot reroots me.....
Did something not go right on the original rooting process? Everything seemed to work with gfree so well.
marine668, I was hoping to run standard for a little while before loading a ROM. I'm *really* happy in the performance coming from a MT3G, so I wanted to wait until I had a good reason to load up a ROM.
So, not the end of the world if I can't permroot, just seems odd.....
lockback said:
A good idea on clearing everything, sadly, same behavior. Temp root works fine, permroot just ignores the fact I hit the button, and reboot reroots me.....
Did something not go right on the original rooting process? Everything seemed to work with gfree so well.
marine668, I was hoping to run standard for a little while before loading a ROM. I'm *really* happy in the performance coming from a MT3G, so I wanted to wait until I had a good reason to load up a ROM.
So, not the end of the world if I can't permroot, just seems odd.....
Click to expand...
Click to collapse
Iced glacier is practically stock, you can try that out. All they did on that ROM is remove the bloat and add a overclock kernel.
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
lockback said:
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
Click to expand...
Click to collapse
the only 2.3 ROM out for the MyTouchHD is CM7.
EVERYTHING else is 2.2 or 2.2.1.
lockback said:
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
Click to expand...
Click to collapse
Iced glacier is 2.2, cm7 and gingerbaked are the only 2.3 roms out that i know of
Sent from my HTC Glacier using XDA App
While the changes in gingerbread are nice, many are cosmetic and will be wasted in a sense ROM. Sure there are some optimizations and some new API's, but really the difference isn't so great that I would say its a must have update. If you like sense, waiting until we have an official 2.3 based ROM to customize is not a big deal. If you want sense, go for Iced Glacier for the time being.
I like it, though currently I am running CM7... I could take either or really.
I actually quite dislike sense. I swapped out the launcher in the first 30 minutes, and booting Sense is a pretty big plus for me.
I think I'll wait until CM7 gets a proper release and go with that.
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Odin is for Samsung Phones and if u lost root redownload the rom or Google super user and download the binaries and just flash them.
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
I tried all that, anyway im in the middle of a stock restore right now and trying to reroot but stuck at the damn visionary step >.<
I am now stuck with S-on and back in a stock rom, downgraded, and visionary still doesnt work, i give up
Try gfree method
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
I believe you got two troubleshootings steps backwards.
After you have searched and exhausted every troubleshooting step you found (which obviously wasn't thorough), you should have posted in the MIUI thread about the problem. They might have scolded you a little before answering, but you would have gotten your answer.
Flashing back to stock is ALWAYS your last resort. It should only be done after scouring the web for answers, then asking for the answer, and when there is no other alternative - FroYo PD15IMG.zip.
Jack is blunt, but as he's as right as always.
I'm not one to deny mistakes, that sure was stupid of me not to look, i guess i just thought there were deeper problems than just the rom having it turned off, anyway i'm doing the downgrade now and it should work, thank you for the help its appreciated
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
Could you point me to this "allow superuser privileges"? I have restored with recovery and have yet to find such a setting.
If you are referring to the permission guard, it allows everything, and there is no setting to simply turn it on
No, not this one. It's been some time since I sold my Nexus One, which was running MIUI back at the time, but I understand that in the newer MIUI there is an app or setting, called LBC guard, which controls both Superuser access and app permissions. Try looking it up.
P.S. I remember CM team member post, saying that the newer CM9 also come with root privileges turned off by default, because they decided it's a safer way.
Right, and the Permission Guard is run by LBC guard, there is no way to set anything different from what i have, i believe its a problem with the busybox binaries and superuser binaries, i'm trying to use this SuperSU instead of superuser to see if that will work. If i remember correctly before all this happened i may have hit uninstall busybox by accident and that may be why its not working, could be that ive never had busybox working and haven't been able to install it due to the SU problem
EDIT: Yes i have solved it now, SuperSU actually makes the prompts for superuser come up now, im using it instead of superuser entirely, must be deeper problems with original superuser
If you had SuperSU installed on the system and additionally installed the regular Superuser, or the other way around - these two are incompatible on binaries AFAIK, and mixing the applications without cleaning up the build and using the correct binary could cause what you were experiencing.
Yes your probably correct only i had two separate versions of superuser that didnt overwrite and that must be where the binaries got messed up
The 1st thing I usually do when I install a new rom, is install SuperSU, update the binaries then I use Titanium to uninstall Superuser.
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Drakona.cookie said:
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Click to expand...
Click to collapse
Anyone else with this problem go in the permissions app and enable root as miui uses its own root for security reasons.
Sent from my T-Mobile MyTouch 4g using xda premium
MIUI uses a customized superuser app. Use it and follow the instructions. Cnote ports the ROM. He knows what he's talking about.
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Droid-2 said:
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Click to expand...
Click to collapse
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
estallings15 said:
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
Click to expand...
Click to collapse
Thanks - I will need to try this later
So, I've been using this video to try and root my Nexus 7. This is my first Android device, and it's not going well.
I've been using the tutorial from "nexus7root.com"
To attempt a root, and I don't have any problems, no errors or anything. Everything goes pretty smoothly, until the end. The first time, it installed and there was a notification about SU permissions being granted, but a root checker said it wasn't properly rooted. Tried to open SuperSU and it said "There is no SU binary..".
So I thought, alright, I'll go back into recovery mode and install the file again. Again, went smoothly but this time when my Nexus booted up, SuperSU was gone.
I could really use some help getting this going properly....
EDIT: FIXED MYSELF