first off, i have a cdma hero and i am running cm 6.1rc now, with classicalgas's theme.
i have weird permission problems going on. it seems like i have halfway lost my root. i can run superuser and all the apps that require root, but i cant modify or change anything in my system folders. typefresh gives me an error that says it cant remount. when i use adb to mount the sd, it says i dont have permission. i get the # but it still says no.
ive also noticed a problem with my nandroids. it worked the other night, but now, twice, it will let me make a backup but it will not restore it. it says there was an error and to do it thru adb.
so, basically, i guess i messed something up somewhere. did i lose some of my root functions? can i re-root, or do i have to go stock and do it all over again? any suggestions? you guys are all amazing for the knowledge on here, so i know someone will help me out.
thanks in advance!
tl;dr-- lost some root functions. do i need to start all over again?
anybody got any ideas ?
I downloaded and installed the Incredible S Beta rom that is listed somewhere on this site for the Incredible. My issue is I want to revert to another ROM, HOWEVER, now my Superuser keeps force closing and will not allow ROM Manger to flash. I try to reboot in HBoot and ONLY get the start-up screen when doing Vol- and Power. Any suggestions on how to get into Hboot or another way to flash a different ROM when SuperUser will NOT allow permissions or Rom Manger wont reboot into Recovery (because superuser forecloses and wont let me flash Rom Manager
BTW-The Incredible S Rom works great...just NO pic/video (As it states in the description.)
Editing to take away some of the clutter (my clutter)
I am not sure what happened. As stated above once the ROM (which is great!) was installed, Rom Manager was no longer granted superuser access (was trying to reboot into recovery via Rom Manager). It wiped the Recovery Version from the phone and would not let me flash a new recovery. Everything else seemed to work fine (superuser permissions, ie. SetPC, etc.)
I tried plugging the phone in and reflashing Unrevoked directly to the phone. Unrevoked stated the root access was denied and asked if I had a "newer firmware".
I also tried uninstalling superuser (to only reinstall and see if it fixed the issue), however, Superuser was included in the ROM and would not let me uninstall.
The only way I was able to get back into Recovery was to re-run Unrevoked Flash and UNPLUG the phone when Unrevoked managed (somehow) to get the phone into bootloader. From there Clockwork ran fine.
Installed a different ROM and all is good.
The only thing I can think of is: In some post regarding the Incredible S being not branded to a certain carrier. When the ROM was installed, it showed "EVDO" in the notification bar (which leads me to believe it is for Sprint), I am not sure how THAT would affect anything being on a Verizon phone...again..only thing I can think of.
Just reboot the phone directly into recovery.
evilkorn said:
Just reboot the phone directly into recovery.
Click to expand...
Click to collapse
It wont let me. I dont think...I tried the Vol-+power...nothing..just reboots. Tried booting into recovery via Rom Manager, but since superuser no longer is granting persmission it wont even do that...is there another way to flash a different ROM?
I just tried reflashing Unrevoked directly to it...it failed to access boot, something about the firmware being too new...???
I dont know anything about your device but maybe your root is broken? Re root and re install superuser goodluck.
Sent from my X10a using XDA App
shahkam said:
I dont know anything about your device but maybe your root is broken? Re root and re install superuser goodluck.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Oh, HTC Incredible.
I went into Rom Manager (and against ALL I have read) am trying to instal and reboot using Rom Manager...instead of going into recovery mode...phone is just sitting here "thinking" right now...nothing YET about being denied root access...fingers crossed...
OK, not sure this was SMART...Hooked phone back up to PC, ran Unrevoked flash kit again...unplugged phone once it came up in recovery...have access NOW to CLockwork...wiped data..installing different ROM as I type...hopefully this will work..
YAY...close call...sorry to waste everyones time..lol. So..If your installing the INcredible S Rom onto your incrediable..I have learned two things...1.) Unrevoked failed to push recovery due to the firmware...2.) you may lose superuser ability....
You would get more help if your thread title would actually be helpful.
Include your phone model, the rom you tried, and what happened (SuperUses FCs[forcecloses]).
Caps, lots of exclamation marks and a title like ZOMFG I NEED HELP, usually deters skilled people from threads like this.
Dark3n said:
You would get more help if your thread title would actually be helpful.
Include your phone model, the rom you tried, and what happened (SuperUses FCs[forcecloses]).
Caps, lots of exclamation marks and a title like ZOMFG I NEED HELP, usually deters skilled people from threads like this.
Click to expand...
Click to collapse
Good point...just paniked. Someone can close this or change title.
You can do it yourself through the edit button. Make it accurate so people who have the same problem and search for it will find your thread and your solution.
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
cwest31 said:
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
Click to expand...
Click to collapse
Read this entire guide.
blackknightavalon said:
Read this entire guide.
Click to expand...
Click to collapse
koooooooooooool
reinstalled sdk following instructions carefully! its not an sdk problem
cwest31 said:
reinstalled sdk following instructions carefully! its not an sdk problem
Click to expand...
Click to collapse
ADB is part of the SDK.
Sent from a message in a bottle.
cwest31 said:
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
Click to expand...
Click to collapse
There is literally no information in this posting that someone can use to help you.
Blackknightavalon's direction to the SDK webpage is about as helpful of a reply as you can expect to solicit with the information you have provided.
This is like going to a car forum, and saying " I have a blue camaro. It won't start. I tried turning the key. Help please"
What commands are you trying to run through adb?
What errors are you getting, if any?
What do you see when you type "adb devices"
What operating system are you running on the computer you are trying to connect from?
Have you turned on "usb debugging" in the options menu on the phone?
There are a whole lot of things that can be your problem, and we'd love to help, but we can't help you if you don't tell us what's wrong.
Doubtless someone else will get back to you before I get a chance to, since my time is very limited these days online, but posting some more information about your problem will elicit a response that may actually help you.
Best of luck!
Blue6IX said:
There is literally no information in this posting that someone can use to help you.
Blackknightavalon's direction to the SDK webpage is about as helpful of a reply as you can expect to solicit with the information you have provided.
This is like going to a car forum, and saying " I have a blue camaro. It won't start. I tried turning the key. Help please"
What commands are you trying to run through adb?
What errors are you getting, if any?
What do you see when you type "adb devices"
What operating system are you running on the computer you are trying to connect from?
Have you turned on "usb debugging" in the options menu on the phone?
There are a whole lot of things that can be your problem, and we'd love to help, but we can't help you if you don't tell us what's wrong.
Doubtless someone else will get back to you before I get a chance to, since my time is very limited these days online, but posting some more information about your problem will elicit a response that may actually help you.
Best of luck!
Click to expand...
Click to collapse
Make sure you have current adb drivers for your phone. It will show android composite in device manager. Fastboot will show fastboot device. Seeing a yellow question mark is bad.
Make sure your pathing is set up right.
Typing "adb devices" and if you see your device. If so you're ready to roll.
I usually get fastboot errors like this when I don't have drivers installed right.
sent from my Agent Orange MT4G Slide using xda premium
Droidmoder said:
Make sure you have current adb drivers for your phone. It will show android composite in device manager. Fastboot will show fastboot device. Seeing a yellow question mark is bad.
Make sure your pathing is set up right.
Typing "adb devices" and if you see your device. If so you're ready to roll.
I usually get fastboot errors like this when I don't have drivers installed right.
Adb is part of the adk. It's to help debug and install things via a directlink to the computer. Its found in platform tools and is considered a dev tool.
sent from my Agent Orange MT4G Slide using xda premium
Click to expand...
Click to collapse
sent from my Agent Orange MT4G Slide using xda premium
I get Error Message with ADB
Hey guys, so I perm rooted with S-OFF my mytouch 4g slide, with theunlockr.com youtube video and guide using revolutionary. then I attempted to install a ROM with ROM MANAGER, and it got stuck on the splash/loading screen. After some searching I found out that this meant that I could have potentially BRICKED the phone, so I followed theunlockr.com's guide to UNROOTING the phone, and it worked, I flashed the original stock tmobile rom, and it loaded fine, I tried to start the whole process again, but now I get stuck in the very beginning, trying to get TEMP root, I start the fr3vo exploit like the guide stated, but then i keep getting error messages on the command line prompt saying that there is an error with ADB, then when I power the phone with volume down and power, the revolutionary is no longer on the top of the screen, but it still says SHIP S-OFF. Does that have to do anything with my problem? is there a way to GET S back to ON, so I can start the process over? or am I better off having S off??? I installed ROM MANAGER and tried to flash a recover image thinking that having S off would allow me to do this, but I get error messages saying there are problems with the permissions. the web site for the guide I used to root is this one incase anyone wants more details into what I did, any help would be greatly appreciated. theunlockr.com/2011/09/09/how-to-permanently-root-and-gain-s-off-on-the-t-mobile-mytouch-4g-slide-revolutionary-method
Use perm root method. Myself I flashed oneclick in recovery, but you can follow the guide the perm root part.
Btw rom manager supports flashing of the new cwm only. I checked the roms in rom manager they aren't supported. You have to go to the cm7 thread here and download and flash cm7 from recovery.
Just redo root process and install cwm from rom manager. Then go to the dev section and flash your favorite rom in recovery. My sig has directions on how to do everything.
Also if you're having permissions error use root explorer on the rom manager apk make sure it has execute checked. Also I think rom manager has a fix permissions button. Its never worked for me.
S off will allow flashing of cwm. However you need to be rooted to flash cwm threw rom manager. My sig has a guide on installing cwm without being rooted.
sent from my Agent Orange MT4G Slide using xda premium
Thanks for the QUICK reply, but I looked at the guide, and it stated I have to have recovery installed, BEFORE I do the perm root method, but I dont have recovery, when I do HBOOT, and I try to boot into recovery, I get a red exclamation mark on the screen and I have to end up taking out the battery. Thats why I was wondering if having S OFF from the beginning now is what is messing me up when I am trying to ROOT again, I mean, I am doing the same steps.... just now I get errors when I try to do the TEMP root step... so I cant continue... and I cant get ROM MANAGER to flash a recovery image... is there a guide or steps someplace that can guide me to root the MT4G slide already having S off?
I found the problem myself, I had to enable USB Debugging.
I had USB debugging enabled.... hmmmm you made me doubt myself... I guess I will try it again, since I flashed stock rom again all settings were reverted... so I cannot VERIFY I had USB debugging on, but I was sure I did... I will try again and post... I am reflashing the stock rom like 5 times a days trying to root again =(
wait... cwest31, you had which same problem? because I was writing about 2 problems: about booting into recovery with S off, but no recovery image (hence I got red exclamation mark), and trying to get ROM MANAGER to flash a recovery image on my phone since I have S off already, but I get error messages (problem with permissions)
RT2023 said:
I had USB debugging enabled.... hmmmm you made me doubt myself... I guess I will try it again, since I flashed stock rom again all settings were reverted... so I cannot VERIFY I had USB debugging on, but I was sure I did... I will try again and post... I am reflashing the stock rom like 5 times a days trying to root again =(
wait... cwest31, you had which same problem? because I was writing about 2 problems: about booting into recovery with S off, but no recovery image (hence I got red exclamation mark), and trying to get ROM MANAGER to flash a recovery image on my phone since I have S off already, but I get error messages (problem with permissions)
Click to expand...
Click to collapse
Umm...did you read the full instructions very carefully? When you get to the part where you flash the Superuser .zip file, you need to try it several times before it'll hold.
blackknightavalon said:
Umm...did you read the full instructions very carefully? When you get to the part where you flash the Superuser .zip file, you need to try it several times before it'll hold.
Click to expand...
Click to collapse
What he said.
Also ROM MANAGER WILL NOT WORK UNLESS ROOTED. Get rooted then try flashing the image. The compendium also has step by step guides using terminal emulator once rooted
sent from my Agent Orange MT4G Slide using xda premium
Also I want you op and the other one to be clear on what s off is and root.
Getting S OFF allows unsigned zips to be flashed. This means you can now flash roms and root. Without s off you cannot root, rom, kernels. S OFF is not root.
Root is gaining admin rights over your phone. this allows programs that require access to the root files to have access to them. ROM Manager, titanium backup, drocap, setcpu will be granted access to the root files and programs which unrooted phones would not be granted access .
This can be a reason why you two are having trouble using rom manager unrooted. Rom manager cannot access the files it needs
sent from my Agent Orange MT4G Slide using xda premium
Please go follow this thread ---> http://forum.xda-developers.com/showthread.php?t=1178606. It tells you how to Permanently root a device that is already s-off.
AWESOME!!! turns out i just had to run revolutionary TWICE, and the second time it figured out it was already rooted and then asked if I wanted to install recovery, I dont know how to do it manually so I clicked yes, and THEN i was able to go into recovery and flash the PERM root ZIP, rebooted and i had SUPERUSER in my app drawer!!!! awesome, now to try to get the version of google talk installed that actually allows for video chat!!! I HATE QIK!!!!!!
DROIDMODER, CWEST31: Thanks so much for the lenghty explanation and help. I have loved android for the ability to customize, and I had the G1, MOTOCLIQ, G2, and now MT4GS, I rooted my G2, but didnt do anything to it because i was scared to F it up, but with the MT4GS I got the balls to do it just because I was SOOOO UPSET that the phone comes with a version of GTALK that does NOT ALLOW FOR VIDEO CHAT!!?!?! WTF!!! whats the front camera for then?! and QIK sucks, not all my friends are on tmobile... i was even more upset when the HTC AMAZE has a version of GTALK that does allow for video chat straight out of the box!!! this is my main push to wanting to root... thanks for letting me vent! lol and thanks for all your great info
RT2023 said:
AWESOME!!! turns out i just had to run revolutionary TWICE, and the second time it figured out it was already rooted and then asked if I wanted to install recovery, I dont know how to do it manually so I clicked yes, and THEN i was able to go into recovery and flash the PERM root ZIP, rebooted and i had SUPERUSER in my app drawer!!!! awesome, now to try to get the version of google talk installed that actually allows for video chat!!! I HATE QIK!!!!!!
Click to expand...
Click to collapse
Your welcome! now procead to install undead's senseless ROM (Best Rom available) and also get rom manager and flash the official CWM recovery! Also proceed to "thank."
mmmm... I tried to install a ROM before and thats what F-ed everything up =/ I am hesitant, I really want a Gtalk version that allows for video chat, does the senseless rom have video gchat capabilities??
I've attempted to root via the root script that uses att servers and it seemed successful, rebooted device twice and said complete, but when I check with root checker basic it says "device not properly rooted." any suggestions where I could be having the problem?
ditchedthefruit said:
I've attempted to root via the root script that uses att servers and it seemed successful, rebooted device twice and said complete, but when I check with root checker basic it says "device not properly rooted." any suggestions where I could be having the problem?
Click to expand...
Click to collapse
You should probably post this in the root thread but if I had to guess you need to go into SU and update the binaries.
In the OP of the root thread it says that if it doesn't work, set your date ahead 2 days, reboot, and try again. Probably would be a good idea to try that.
I actually did reset the date before creating a thread. In the OP it says to do that if you become stuck at the ... screen. I didn't get stuck. WHole process went through like clockwork, said complete, rebooted automatically and now, well i dunno. Phone works fine, just don't have a super user.
Try it again.
go in the dev forum and follow one step root instructions...did mine the other day. have to set date ahead like mentioned above and re install the root like 3 times before it works.
I was able to do it using the steps outlined in this post.
http://forum.xda-developers.com/showthread.php?t=1678138
ATT One X 1.85 Root Successful!
To all the "try it agains", thanks! Being new to android and rooting i wasn't sure how to read what was happening, but after a lot of google-ing (with results that said try again, set date forward etc..) and really trying to read all the script, I finally got it! For the other noobs that come to this link... continue to re-run the root process exactly as the instructions say. It will take a sitting session of doing the exact same thing 3-4 times. Each time it is rooting or installing another package. It took me MUCH longer than it should have because I wasn't familiar and more importantly, wasn't paying attention to the script, you have to look at more than the instructions on web page. Unlocking bootloader is very simple as well, given that you can look at exactly whats going on in front of you! Thanks again to all the developers and posters that make it easier on a rook like me!
So I have a Moto X and I rooted with this method: http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059
I can grant access for root apps but when I get prompted to update the SU Binary upon opening SU by Chainfire, it will fail if I accept and tell me to reboot and try again.
However, when I reboot and try again, it only gives the same error continuously. Could
it possibly be because it's only a temp root? I don't think that would be the reason but
I'm not entirely sure....
Any help greatly appreciated. Thanks.
Also, apologies if anything was done wrong with this thread. I'm not used to forums so
please correct me kindly on my mistakes if any were made.
XVaVX said:
So I have a Moto X and I rooted with this method: http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059
I can grant access for root apps but when I get prompted to update the SU Binary upon opening SU by Chainfire, it will fail if I accept and tell me to reboot and try again.
However, when I reboot and try again, it only gives the same error continuously. Could
it possibly be because it's only a temp root? I don't think that would be the reason but
I'm not entirely sure....
Any help greatly appreciated. Thanks.
Also, apologies if anything was done wrong with this thread. I'm not used to forums so
please correct me kindly on my mistakes if any were made.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
Are you sure to have followed correctly the instructions?
...
Yeah, as far as I know I followed every one correctly.
Still a newbie...
Sorry, I'm kind of still new to rooting. Do you have a tutorial on how to flash things such as those onto my phone? I tried to find some tutorials but most of them consist of just third-party apps that don't flash it on. Also, can I still flash those on my phone even though I only have a temporary root instead of a permanent root?
nilac said:
Hi and thank you for using XDA Assist
Are you sure to have followed correctly the instructions?
Click to expand...
Click to collapse
Lol my bad. I realize now that this doesn't exactly relate to rooting. Anyways, I have unlocked my boot loader today and now I'm having issues with the TWRP recovery. I flash and install it and everything goes smoothly but it won't actually boot into recovery....
I have tried both the TWRP Manager app from the Playstore and I have tried the adb way. Both of them flashed right and installed but they won't actually boot into recovery. It just boots and gives me the warning about the unlocked boot loader then shows the warning again and boots up like normal. Do you have an idea as to why it won't boot into recovery?
Edit: I've got it now. Sorry for all the trouble.