Related
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
anon1ski said:
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
Click to expand...
Click to collapse
Download cyan's recovery 1.4 to your sdk tools folder, start the phone in fastboot mode [back+power] folder and run:
Code:
fastboot boot cm-recovery-1.4.img
That should boot the recovery image and you can work from there to reflash whatever you want.
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
anon1ski said:
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
Click to expand...
Click to collapse
Errr... you don't have the sdk?
You don't use adb...?!
That's like trying to play football with no limbs..
Get yourself rigged up with this:
http://developer.android.com/sdk/1.5_r3/installing.html
btw.. you won't need to set up eclipse or the adt plugin for this, just make sure your environment variables and java paths are set up as per the guide.
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
anon1ski said:
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
Click to expand...
Click to collapse
I do a lot of stuff from my phone too tbh, Somehow it satisfies my geek cravings more fully.. But adb is massively useful when you're on the pc.. saves a lot of cramped typing on the device keyboard.
Fastboot will be your saviour in this case though, and you're gonna need a proper box to run that on.
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
anon1ski said:
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
Click to expand...
Click to collapse
lol.. adb is pretty simple.. a few examples:
Code:
adb push localpath devicepath # push files to your phone eg: adb push c:\update.zip /sdcard
adb pull devicepath localpath # pull files from device
adb shell # basically a terminal running on your device that you control from your pc.. im sure you can figure this out if you do everything from your phone.
adb shell reboot # guess?
adb shell reboot recovery # go straight to recovery without holding any buttons
fastboot should be in the same folder as adb.. you can use it to flash .img files from the pc or just boot the images without flashing them.
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
anon1ski said:
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
Click to expand...
Click to collapse
Assuming you're on windows, you'll have to install the adb driver first (not the standard android that windows installs automatically, theres a seperate driver in the usb_driver folder of the sdk). You also need to enable usb debugging on your phone.
Follow this guide if you need to:
http://forum.xda-developers.com/showthread.php?t=532719
You can use adb whatever mode your phone is in.. even when its stuck in a bootloop usually. You don't need to be running anything on the phone, the drivers are switched on by init.rc.
Fastboot can only be run with the phone in fastboot mode (surpisingly).
thanka alot man. im gonna give this all a try.
Good luck
ok. got adb running. ran the command you gave me. it brings up 1.4 but doesnt push it to my phone...... can i actually INSTALL 1.4 from fastboot/adb?
nevermind. figured it out. used common sense and just ran fastboot flash recovery recovery.img and it worked. thanks for everything
my super user still wont work.; so apparently it had nothing to do with the recovery..... im going to wipe, reflash cyan 3.9.1. and see if that works.
So I flashed SuperD yesterday, and all is cool. Its not my first time using roms, and everything went smooth.
But then today I wanted to change the keyboard layout back to the German layout. So I went to Terminal Emulator and began to edit the layout using this method (tested, working from these forums)
su
mount -o rw,remount /system
cp /sdcard/trout-keypad-v3.kcm.bin /system/usr/keychars
Anyway, once I finished, it said that this operation isnt possible. Then I realized that I forgot to put the file on sd card. So I added the file, but then the strange part came....
I then again went into terminal emulator and typed "su" to start the process again but now im getting the "permission denied error! 5 min ago I didnt have this error and could mount just fine! The phone is running fine, but it seems like I ve lost root.
Do I need to reflash the rom or the spl to reverse this? I really just need access to Terminal again. Anyone know how to fix this? I tried rebooting just to see if it was some type of bug, but even after reboot Im still getting permission denied.
Could really use some help on this!
Use adb shell. Try clearing the saved options in the SU application. Try a different terminal program. Lastly, try to just reflash the rom.
evilkorn said:
Use adb shell. Try clearing the saved options in the SU application. Try a different terminal program. Lastly, try to just reflash the rom.
Click to expand...
Click to collapse
I installed a new Terminal, and it seems to work fine. Might seem like a dumb question, but Im really not sure if I have root or not?!
If it worked what's the question?
evilkorn said:
If it worked what's the question?
Click to expand...
Click to collapse
Your right. Was a dumb question. It just confused me, as one terminal is giving me access, and another wont. Guess its just a bug.
Anyway, I reflashed the rom, and all is perfect. Thanks for the help though guys.
I'm having serious issues with my N1 since receiving it back from HTC for a repair. I had rooted the phone before it was repaired for a crack in the glass, but the repair center had re-locked the bootloader. I followed steps the way I had done before to root my phone and succeeded in re-unlocking bootloader but when I did superboot (using mac terminal) did not come to screen where root permissions were offered... booted phone, no wifi signal, did not recognize sd, very glitchy, unstable and maybe worst of all unable to mount to computer. So I don't know if anyone with this small amount of information would have any clue as to what I can do. Oh yes and when I had gotten my phone back from repair center I had done update to FRF91.. so I know I'm an idiot for trying to use superboot when there isn't one for the FRF91. There you go gentlemen. If someone is willing to help I can provide any other information required.
As long as you can get to your recovery screen, you're not bricked. Most important, are you running a custom recovery like Amon_RA's?
Edit: If you have a stock recovery and want the superuser/unsecured boot use the updates from here
-If you have a custom recover just flash a ROM that includes superuser/unsecured boot
*Always do a Nandroid
I didn't have it before I unlocked my bootloader, and I can't seem to install it considering that every post says you put it on the sd.. and as I said I cant even mount my phone So apparently I'm on stock..
Micro SD adapter?
That does make things interesting, the only thing i can think of is getting a Micro-sd adapter and putting the update on the sd, then place the sd back in your phone and flash.
Thread moved to Q&A.
Can't you adb push the file while in the recovery menu?
I can't flash if I can't mount my sd card right? So that would make the ROM with superuser useless.. Can you think of a way I can get Amon_Ra recovery through bootloader?
I can't flash if I can't mount my sd card right? So that would make the ROM with superuser useless.. Can you think of a way I can get Amon_Ra recovery through bootloader?
I've heard about this but I'm a total n00b, don't know how to..
I was referring to the adb push.. any help with this would be GREATLY appreciated!
ADB method
If you still have the adb ability try fastboot flashing...just follow the steps here
Emul8tor I really appreciate the continuing advice- home from work now.. I can't seem to get adb if i have done everything correctly working on terminal mac os.. have android sdk and i should be running it under sdk/tools dir correct? i type in adb or adb devices and I get adb: command not found..suggestions?
Have you used the adb method before, kinda sounds like you haven't set the PATH for your environment. I don't have any clue about the set-up for Mac, but theres a tutorial here
okay going to read through this again especially part on creating the PATH.. back soon
really don't know what to think I have no idea how to create a .bash profile and I'm not so sure this is why adb isn't working. Thoughts?
and I didn't use the adb method before.. only fastboot
found this by googling, adding tools to your path lets you run Android Debug Bridge (adb) and the other command line tools without needing to supply the full path to the tools directory when typing commands in Terminal
Dude this guy's having the same problem as me, I guarantee you he used the wrong version superboot with FRF91 http://androidforums.com/all-things-root-nexus/127689-please-help.html
I'll bet he can't mount sd card either
Alright I ran adb command but it isn't registering the phone after list of devices attatched. But it did issue a string of commands after so I assume it is working... Now i guess I can say that I am truly scared because my adb doesn't even recognize the device.
Just a hunch...is debugging enabled on your device?
GRRRRR SuperOneClick breaks it also
I hate posting a question, but I've exhausted searching for an answer.
I have a G1 that i am trying to root in order to flash, I made the mistake of using ANDROOT because it said it worked for G1. Well it said it rooted my phone, but I think it botched something internally because I can't actually get root access.
I then attempted to use the SUPERONECLICK and it ran through the whole proccess and failed when it did a test command at the end to send a SU request.
I then tried some other things to flash clockworkmod recovery with no success.
Now when I attempt to access root in terminal I get...
"371 could not load needed library 'libbinder.so' for 'su' (lLibrary 'libbinder.so' not found)CANNOT LINK EXECUTABLE"
I'm not an idiot, I've rooted and flashed both the NEXUS ONE and CAPTIVATE many times problem free, but this has now got me stumpped and I've searched to no avail. Any help is appreciated.
I'm having the same problem.
Path I took was a bit different, just got here from WM some Linux exp not much.
I tried universal androot
It said it worked. But it didn't.
Then SuperOneClick
Failed at SU test.
So i tried the Shell Root that said it worked.
Only proof I have that it works is that android screen cast works.
Then I was installing Titanium and it said I didn't have root or my busy box was not installed. So I pushed I'm having trouble ... I downloads it.. to where i dont know
I tried pushing it from command prompt with
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
at this point I get that error
when I exit and come back into shell I get the same error just by typing SU.
Any help would be appreciated it. I have a Zio
What's a zio?
To both...start over with the DREAIMG.nbh and just start from scratch. These one clicks may work but they're boring. I actually unrooted one of my dreams and used visionary and it worked too funny (but boring)
htc vision
Title says it all. While trying to learn some theme tricks, I must have screwed something up in the framework, because I'm stuck in a boot-loop after rebooting.
Thanks to Aria's post, which describes an easy way to make an easy ADB shortcut, I'm all set to go with ADB... but how can I force my cell to mount my computer when it's turned off? I just need to push my backup onto my phone, because I copied my CWM backup onto my pc and deleted it from my cell to make more room for videos. Stupid, I know
Any ideas? Thanks!
Nevermind, I fixed it through CWM by flashing a .zip of part of the framework that I changed, and it rebooted fine after that. From there I could mount my device.
Still, I'd be curious to know how to mount a device that cannot boot properly, if anyone knows a way.
how did you fix it i am stuck on lg logo when i boot i would really appreciate any help you could give
Komodo Rogue said:
Nevermind, I fixed it through CWM by flashing a .zip of part of the framework that I changed, and it rebooted fine after that. From there I could mount my device.
Still, I'd be curious to know how to mount a device that cannot boot properly, if anyone knows a way.
Click to expand...
Click to collapse
You can mount the system like this. If it's in a bootloop and ADB is enabled, this'll work.
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
Sent from my LG Thrill 4G