Hey guys,
Recently rooted using unrevoked and wifi tether was working but after updating superuser to 3.0.7 tethering no longer works and asks if I have root? It says S-OFF in the bootloader. Tried to run unrevoked again but it failed to get root access. Also tried clearing cache and data but still no luck. Any ideas? Thanks.
Running 2.2
Open the Superuser app and make sure permissions is on, then reboot
still no luck. I tried z4 and temp rooted and it seems to have added the permissions to superuser but after reboot same thing happens. I guess the apps cant see the root?
Might try to downgrade superuser to like su-2.3.6.2-efgh by flashing within recovery and then go back in and updating from market.
If you're S-Off, you don't need to keep trying to root. You're rooted.
What I would do is make sure you have Amon Ra for recovery, wipe everything as outlined in the guide I wrote (link in my sig) and flash a ROM. That will give you SU and you should be fine.
Just clearing Cache and Data is not enough. You need to clear Dalvik Cache, System, etc...
tried this and it didnt work for me.. any other suggestions?
bossman1 said:
tried this and it didnt work for me.. any other suggestions?
Click to expand...
Click to collapse
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip flash this in recovery
Related
this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...
Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App
i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol
can you boot into fastboot or Android Recovery?
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?
i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.
you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!
Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.
just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!
Sorry, this question was posted in the wrong thread and cant find how to delete it myself, either delete or move. sorry again.
Not sure how this happened, but i lost root access to my 3.2 (was a acerstock+root variant) but still have CWM access. What is the easiest way to get root back?
as long as you still have a copy of the same ROM, you could boot to CWM, wipe only cache + dalvik-cache and flash the ROM again. you won't lose anything and should get root back. Also, first thing you should do after that is open Superuser and update the su binary.
When i go to do a dalvik-cache wipe, it gives me an error
E:unknown volume for path [/sd-ext]
and then when i reflash the ROM i still dont have root.
That's fine with older versions of CWM. It will still wipe fine. Moving on...
1) are you sure the ROM you're flashing is supposed to be rooted?
2) just to be sure, which ROM is it exactly?
3) do you even have the Superuser app?
4) if yes, what happens when you open it? Can you update the su binary?
I'm going to guess, the user installed the factory update or rom to 3,2. Based on the fact he/she didn't really know what they had to begin with....
There use to be an update.zip with su and super user.apk. If you still have cwm I would be looking for that. Last place I saw it was a Motor Droid forum.
I loose root every time I try to update busybox. I just restore a backup to regain root.
Sent from my A500 using xda premium
Hi, so I decided to install CM11 on my nexus 4, but before that I had to unlock the bootloader and root. Bootloader unlocked succesfully but I couldn't root or flash a ROM cus the zips are not in my sdcard and I'm stuck without a ROM (phone just plays boot animation continuously). So I searched about adb push command, tried that and according to my CMD window it works, but in CWM when I try to install from zip, the zip isnt there.
cwm is latest version so thats not the issue. Solutions proposed by other threads arent working either.
Any ideas?
Thanks in advance.
EDIT:
I have used the guide in this thread
http://forum.xda-developers.com/showthread.php?t=2266654
It seems like this person has run into the same problem as me, but no one answered on the thread either.
r8revealed said:
Kind of an urgent problem as well, A friend of mine has had a bootloop on the Nexus 4 using this guide.
Upon installing CWM, the phone fell into a bootloop (Superuser hasnt been installed yet). After that, just in case, we did a Wipe data factory reset, wipe cache partition, and then wipe dalvik cache and no luck. The device has an unlocked bootloader and everything else went flawlessly. What can be done now to get the phone rooted and up and running? (An unroot is a possible solution, but maybe something else can be done so that an unroot wont be necessary).
Click to expand...
Click to collapse
Guys I found a solution.
You can use a toolkit by wugfresh found at http://www.wugfresh.com/nrt/ to revert to stock.
thanks anyway!
So I was flashing ICS onto my xt535 to try and load a custom rom and now my phone is on the latest version of superuser, and it crashes all the time. Unfortunately i also need superuser permissions to load the custom rom. I am currently on SU version 3.2 but i have heard that ver 3.1.3 doesnt have the same issue with crashing. I have the files to flash the earlier version but the only APK that i could find to do it was ROM Manager, which as i'm sure everyone is aware, requires CWM. From what i've tried it seems that i need SU to load up CWM, but i need CWM to load the earlier version of SU. also i am quite new to the android programming scene but i have some previous experience in C++ and C#
Anyone got any Ideas on how to fix this?
Try clearing data and cache of su app?
arora.ujjwal said:
Try clearing data and cache of su app?
Click to expand...
Click to collapse
i tried that. after clearing the cache and the data i open up superuser to run it, and it says, "Unfortunately, Superuser has stopped." after that it says that every time i open superuser from then on.
Sonikfyre said:
i tried that. after clearing the cache and the data i open up superuser to run it, and it says, "Unfortunately, Superuser has stopped." after that it says that every time i open superuser from then on.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1827338
Check the 'Revert Back to GB' section in the above post. They have an SBF, you can flash it by putting your phone in download mode and use RSD lite to flash the SBF
CM11 doesn't seem to have root. I've flashed the latest nightly and for whatever reason, it just doesn't want to work right. Can't delete installed apps, can't remount, or anything...I can't be the only one can I?
RavenII said:
CM11 doesn't seem to have root. I've flashed the latest nightly and for whatever reason, it just doesn't want to work right. Can't delete installed apps, can't remount, or anything...I can't be the only one can I?
Click to expand...
Click to collapse
Probably, the problem is the app you're trying to use...
RavenII said:
CM11 doesn't seem to have root. I've flashed the latest nightly and for whatever reason, it just doesn't want to work right. Can't delete installed apps, can't remount, or anything...I can't be the only one can I?
Click to expand...
Click to collapse
Did you install a custom kernel after flashing the rom?
diogo.sena said:
Probably, the problem is the app you're trying to use...
Click to expand...
Click to collapse
It's got to be a system thing, even adb won't remember when I authorize my computer....
jrosetto said:
Did you install a custom kernel after flashing the rom?
Click to expand...
Click to collapse
Negative, stock kernel. Clean install...
My suggestion is to get the latest TWRP or CWM and factory reset, wipe system, and delvik cache. Then flash the rom again. It is possible you also have a corrupted download. Use an MD5 checker on the ZIP to make sure it isn't corrupted. If you don't want to start over you can also flash the auto root from chainfire from this link.
http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip
So I got around to it. Clean wipe, fresh from the start, install latest nightly of CM10, gapps, and no go. It says it's giving romtoolbox Pro permissions, but it can't delete anything. I authorize the computer to communicate through adb, and it forgets after a reboot...
The only thing is that I'm running Philz touch latest recovery...
Have you tried installing supersu? I found that a lot of apps have problems with the default super user.
I guess your /system doesn't have the right permissions. It's maybe set to read only.
IF not.. > Check your developer options and give root access to adb and apps