rooted my phone today and most of it went well. both rasio s and eng s off.
i have installed rom manager and have encountered a problem. Before I chose and downloaded the rom i wanted, i saw a few posts about formatting and resetting on the first time flash so i rebooted into recovery and did so. unfortunately now im left with a phone running 2.2 and cant flash! i had to reinstall rom manager after the reset and whatever i do in rom manager is saying its umable to run privileged commands i.e root?!? do i need to downloaded visionary again and repeat the whole process cos i thought i had perm rooted! any ideas??
thanks
If you head to Settings > Applications > Manage Applications
Find Superuser and "Clear data" then fire up ROM Manager as normal. It should ask for SU permission if you try to perform a root command.
thanks but all sorted. restored original rooted image and just flashed cm7. thanks anyway!
Related
Hi,
I'd like to start off by saying that I've flashed my Desire numerous times and it works fine, but I recently flashed my brother in law's and it's been acting up.
I followed one of the noob guides (root, s-off with alpharev) and put bravo_alphaspl-cm7r2.img on the phone.
I then flashed CM 7.1 (and also a bunch of other version). The flashing works fine. I reboot and when I go to rom manager and click on download roms it gives me the error message: The application ROM Manager (process com.koushikdutta.rommanager) has stopped unexpectedly.
Also if I flash google apps from recovery it flashes fine, but it crashes in CM.
What's I've tried:
-reflashing
-davlik
-fixing permissions
-redownloading all the files and reflashing (including md5 check)
I can't remove rom manager and reinstall it since it won't let me remove it.
Any ideas what I can do to fix this? I searched online and there is no concrete answer. Everybody seems to be guessing a solution, but so far no success for me.
Yes this is also the issue with my Desire and the solution is to reinstal Rom manager.
This worked for me.
Cheers
Nobody needs Rom Manager. All operations can be done with other and better software (recovery, GParted). Furthermore, it causes more problems than it solves.
So just uninstall it and never use it again.
but how do you uninstall it? there is no way to remove it from applications.
also google apps crashes when installed.
nevermind...now no error message anymore. No clue why.
Hi All! I used the method that involved booting CWM and running a root .zip, and SU seemed to work fine for a while.
But lately (as of the last two days (rooted it three days ago)) Apps started hanging at the "Acquiring root privileges".
I have tried uninstalling updates to the SU app, and clearing data, but it still does it. (uninstalling updates renders it completely un-usable as the binary has been updated.)
SU does occasionally work, but I can't pinpoint why.
Thanks!
NRoach44 said:
Hi All! I used the method that involved booting CWM and running a root .zip, and SU seemed to work fine for a while.
But lately (as of the last two days (rooted it three days ago)) Apps started hanging at the "Acquiring root privileges".
I have tried uninstalling updates to the SU app, and clearing data, but it still does it. (uninstalling updates renders it completely un-usable as the binary has been updated.)
SU does occasionally work, but I can't pinpoint why.
Thanks!
Click to expand...
Click to collapse
Do you have a recovery installed like clockworkmod? If so boot into recovery and select 'fix permissions'. Not sure if that will help but its all I could think of :S
james44422 said:
Do you have a recovery installed like clockworkmod? If so boot into recovery and select 'fix permissions'. Not sure if that will help but its all I could think of :S
Click to expand...
Click to collapse
Well, instead of putting up with that, I took the plunge and installed FXP137-CM10, and as that seems to be causing different issues, I'll start a new thread. Thanks anyways.
OK, I know this has been asked and asked again, but I have been reading and digging and googling for several days now, and cannot find a solution.
I've got a JB S3 At&t, and wanted to root it, so after reading for a few weeks, I got the "Samsung_Galaxy_S3_ToolKit_v7.0", donated, and got 7.2 (newest version). I flashed with the toolkit to get an unsecured boot image, with SuperSU 1.04, busybox, and TWRP .
Root happened fine. The phone booted, and when I went to open SuperSU (the icon was in my apps), it asked to update the binaries. I said yes, it failed, and the app opened anyway to allow me to access the options. Triangle away worked fine.
The update binaries thing was bugging me, so I updated to SuperSU 1.10 via google store, and the same thing happened, but now I could not access the program after the binary update failed. It still works (triangle away asks and gets permission) but I could not access the program any longer. It just closes after it informs me that updating the binaries failed.
I have tried installing the program as an app, pushing an APK, and installing a zip from recovery. No matter what I do, it ends up the same.
I have also re-flashed the boot several times, and tried a different method using Odin directly and CF-Root. (seems to be the only way to uninstall it) I have tried numerous combinations, but to no avail. I feel like I have done everything I know how to do short of an unroot to stock and try again.
Any helpful suggestions are welcome.
I'd like to be able to use the program, but this is turning into an OCD nightmare. I'd post this in a development forum, but do not have enough posts yet.
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
illmatic24 said:
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
Click to expand...
Click to collapse
Thanks. I ended up doing it the hard way. (I swear I had auto email notification enabled here, or I would have seen your post and tried it)
Anyway, I cleared caches/userdata/wipe cache partition first, then flashed a stock unrooted 4.1.1 rom from here,
Then I used CF-autoroot, and low and behold, SU was showing up as an app. (it was not previously when I used CF-AR)
I let it update itself and bam, it works! Installed adbd insecure, and it works too. (it was not showing up as an app when I did it before either)
Next I added TWRP 2.4.3.0. and everything still works!
Either the stock AT&T rom on this unit had something interfereing with root, or the root image I used in the toolkit has an issue. I'm leaning towards a toolkit issue since when I used it and it installed TWRP 2.4.1.0, I could not get into recovery, just a black screen.
I lieu of this, I'm limiting my use of the toolkit.
Curiously, the toolkit also allows a sideload via TWRP/CWM, but does not provide a driver. Windows 7 cannot recognize the phone in recovery mode with a custom recovery installed, although it does when a stock recovery is. I have yet to find a driver.
Hello,
So as the forum discussion I have the AT&T S3 I747 - Initially I rooted the phone to be able to use it at as a wireless hotspot and everything worked great the method i used was galaxys3root .com (I cant post the actual link <10 posts)
What I thought was a notification OTA triggered me to opening superuser and doing an uninstall/permanent unroot to ensure i didn't brick my phone, well I was wrong about the notification feeling like an idiot i decided to go ahead a reroot the phone again.
I followed the same procedure as linked above this time with problems, I have no Superuser Icon in apps tray, under applications manager it appears but only gives me the option to "Uninstall Updates" and that all
Things I have tried
- installing both versions onto the phone Clockwork mod simply just sits there under "Installing Superuser" Chain version installs but appears to do nothing.
- Used odin to reflash the stock rom then tried the re root process again
- reinstalled the wifi app to see if working but no longer is
I am not looking for a custom rom I like the default one I have I just want the Superuser app to show up again, anyone know what I could do to fix this?
Thanks for all your help
Flash the rooted stock version with Odin
mrhaley30705 said:
Flash the rooted stock version with Odin
Click to expand...
Click to collapse
Thanks for your reply I seem to have got it solved. I downloaded a File Explorer Went into system/Apps found the SuperUser APK opened it, let it install updates and what not after done the app showed back in my apps drawer, installed my wifi mod and superuser granted permissions so everything is good
Questions and help issues go in Q&A and Help section
Thread moved
FNM
Hello ppl. So, I was playing with my old phone, Sprint Samsung Galaxy Note II, (it's always a good idea to torture old phones instead of the new ones, right?) and I've done a lot of stuff with it, but for a long time, nothing was happening. So, this is the list of what I did with the phone:
0. I had my original OS rooted, then unrooted it, and I was said to use twrp, if I'm not wrong (can look up, but it will take time).
1. Rooted it. Knox disabled root. (I had the latest, NC2, update)
2. Tried to flash the older OS. It wouldn't. I guess because of Knox.
3. As I was trying to flash older OS, I kind of lost the OS, and had no OS at all. No problem, I thought. I'd just download and flash several other versions of OS, and eventually I'll find one that'll be working
4. It appeared to be the latest, NC2.
5. Back to root. Until restart.
6. Whenever I root, I try to install cwm with ROM Manager. Upon restart, the recovery is <3e>. Not <2e> or cwm. Not even twrp that I had.
7. So now I'm here, and I just don't know what to do. I remember that I somehow disabled the knox, and I'm sure just by updating the SuperSU (or its binaries? But I can't find any in the market), but this CF-AutoRoot installs latest SuperSU, and so there is nothing to update.
Then I finally figured out what to do. I should warn you, it took me 3 days to figure out what to do to install CWM, so if you have any kind of a problem with installing it, just use this tutorial, I guess. Even though it covers just the basics.
1. In SuperSU, choose "Uninstall to install other Superuser application" or similar.
2. It was necessary for my phone to actually update binaries
3. As the Knox was disabled by updating the binaries, I could now use ROM Manager to install Clockworkmod Recovery (Yay!!!)
4. Download the Cyanogenmod ROM, either through ROM Manager or the web site (choose most stable and recent. Otherwise, who knows what problems it might have) and install it:
4.1 In Clockworkmod (CWM, cwm) (if you still haven't copied the Cyanogenmod (CM, cm) and Google Apps to your external SD, please do that. Just restart the phone and copy it from your computer. Download from the web site) (Vol Up, Home, Power from the phone turned off) just choose the right update and press to install. Then do the same for Google Apps.
4.2 In ROM Manager, just choose the CM and don't forget to install Google Apps.
5. When my phone actually installed Cyanogenmod, it loaded forever. As I was sleepy, I don't actually remember what I did, but I reinstalled the ROM several times, and finally, it worked.
6. Now I'm enjoying my old phone that uses Cyanogenmod.