Develop Bugs

[Q] How exactly do I flash amon 1.8 recovery?

I've tried reading through the thread many times already.... Renaming the file, moving it to different locations, going through the terminal. Yet I'm still not able to install the 1.8 recovery. I have no idea how to use the abd shell or what ever it is, I don't even think I have it. Could someone upload a flashable zip with it? Or maybe give me some step by step for it cause I'm lost here and want to flash Vael's rom.

1) Put the recovery image on the root of your sdcard
2) Open a terminal emulator on your phone
3) Type "su" and hit enter
4) Type flash_image recovery /sdcard/<name_of_the_recovery_image>.img and hit enter
Voila! You just updated your recovery image

even easier..
download rom manager from the market, you must be rooted to use, hit flash recovery, then it will flash clockwork recovery, once thats done, scroll to the bottom on the main page of rom manager, then select flash alternate recovery, and it will flash amon 1.8.0. This is the easiest way to do it

It says I don't have permission everytime I try the terminal.
On the plus side the Rom Manager solution was simple and effective. Though I would still like to know why I don't have permission through the terminal and a little more about the problem I was having. It would be nice know what exactly is going on and how to fix these little problems.

crimeslunk said:
It says I don't have permission everytime I try the terminal.
Click to expand...
Click to collapse
Try re-installing the SU app from the market. I've had trouble with it being bundled in roms before, reinstalling it has always fixed my su permission issues.
Reboot your phone after you get the SU app reinstalled.

Maybe this could help for you:
http://forum.xda-developers.com/showthread.php?t=764062&highlight=amon_RA

[Q] No USB functionality, including USB Fastboot

My HTC Desire has no USB functionality at all, including USB Fastboot. It's also got no root access. There's no known reason why this occured.
Similar forum threads suggest that USB functions can be restored if I revert to the stock RUU image. It's possible that an update has been the cause of this problem.
I've tried to install the base ROM - RUU, but because I have Hboot 0.93 I have to downgrade, but can't do that because there is no existing root access and I don't have ClockWorksMod recovery installed to get around the signature verifications.
The device boots up and operates fine (even the SD Card). I have to charge the battery using my partner's phone and can't do any data transfers. I'm running Android 2.2, Radio 32.49.00.32U_5.11.05.27, Hboot 0.93
I'm beginning to think that the motherboard has somehow been fried and can no longer supprt the USB part of it.
Any ideas would be most helpful. Thanks heaps

As you are unrooted, you should have warranty and that is the first way to fix it.
The other is a bit more complicated but if you are cautions, you'll be fine. Use this guide:
quanchi said:
...
This is a specific situation - usb brick and totally stock rom, recovery and hboot. It's not required for people who have a modified recovery and a rooted rom. It's easy like 1-2-3.
Before doing anything else enable the Debug Mode in the Applications / Dev menu
1. Download the rageagainstthecage exploit from the authors site:
http://c-skills.blogspot.com/2010/08/please-hold-line.html
2. Download the flash_image and misc (mtd0.img) partition image from this thread.
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
Modify the mtd0.img according to your phones CID (how to get the CID also explained in the thread)
2. Download Android Terminal Emulator from the Market
3. Copy the exploit binary (rageagainstthecage-arm5.bin), the flash_image and modifed mtd0.img to the sdcard via an external card reader
4. Start the Terminal
5. Copy the files to the Terminal app data directory (the only place on the data partition you will have write access while running the Terminal), and make the binaries executable
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/shared_prefs/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/shared_prefs/mtd0.img
cd /data/data/jackpal.androidterm/shared_prefs/
chmod 755 rageagainstthecage-arm5.bin flash_image
6. Run the exploit
Code:
/data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
After the exploit exits/finishes there should be a short system freeze, followed by inablity to issue any command from the terminal (don't worry). Exit the Terminal by long pressing HOME and force close the Terminal app from the Application Manager
7. Start the terminal again, a root prompt should be visible
8. Flash the misc partition
Code:
cd /data/data/jackpal.androidterm/shared_prefs
./flash_image misc mtd0.img
9. Reboot
...
Click to expand...
Click to collapse

No luck unfortunately, one of the steps requires the CID, and as you know I have not got USB to access fastboot mode.
Is there any other way to get the CID?

You should read the whole thread for the usb-fix
If I remember correctly you should use "cat /sys/class/mmc_host/mmc1/mmc1:*/cid" (without quotes) command from the terminal emulator.
The terminal emulator in your case will be the substitute for the fastboot, so everything is done via the former.
If you click the link to the quote, you'll see that there are number of people who got it sorted using this method. So just be patient and do the reading.

Ive got same problem, but have fastboot access.. Can I use regular terminal in windows then?

Well, you can use it to find the CID ("fastboot oem boot"), but the other commands in the guide quoted above are for a terminal emulator and are not the same as the ones used with fastboot. So in order not to get confused I recommend you to just use a terminal emulator, it's not harder than fastboot.

Well, i figured out that one on my own.. At least I learn something of this.. Anyway, when i try to execute first command in emulator I just get up "cannot create, directory nonexistent. Ive tripple checked the commandlines.. What could be wrong??

bump.........

Well I followed all the instructions, could get temp root access and flash a modified mtd0.img (which had the correct CID and Rom version) but still no USB. I tried it several times over and can't get anywhere. The hardware must be cactus! Time to throw it over a cliff !!

[Q] ADB Shell Won't Allow me to run as SU

So I'm trying to get into su to run gfree_verify to make sure my permaroot S-off/SIM card unlock/SuperCID was successful, but I'm getting a permission denied error.
What happens is, I type adb shell, then I type su, there's a really long delay, then it tells me Permission Denied. However, when I run the Terminal Emulator from my phone and type in the su command, I get root access just fine.
I used the "official" method that is on the HTC Vision Wiki that is located here. The only thing, however, is that my Android SDK install wasn't installed using any type of installer. I just extracted a zip file and shoved it in a random folder. I did make sure to run the Command Prompt as Administrator before issuing the adb shell command, but I'm still unable to get superuser access through the PC. Trying to use the adb root command gives me an "adbd cannot run as root in production builds" error.
Did I do something incorrectly?

adb kill-server
adb start-server
See if that works. If not, try rebooting your computer.
Sent from a Western Union telegram.

Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?

steviewevie said:
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
Click to expand...
Click to collapse
I rebooted the daemeon, computer, and also the phone. No dice.
The Superuser app is correctly installed. When I ran Adfree and attempted to go into SU in Terminal, I got the usual Allow Superuser access dialog. Both worked without any problems; like I said, I can get root access from the on-the-phone terminal, it's when I attempted to get root access from the adb shell command on my computer where I have problems.
No special ROMs, completely stock post-November OTA update. The only thing I flashed after permarooting was the Clockwork Recovery mod, but adb shell SU wasn't working before this. I initially used some outdated instructions (involving the use of the dd command, and the wpathis.ko or something). I read some more and learned these were out of dated, so I unrooted. I then used the instructions that are on the wiki using gfree to permroot.
gfree_verify works without any problems if I run it from the Terminal Emulator on my phone. Returns the proper values to indicate I'm SIM Unlocked, SuperCID, and S-off. I'm glad it works, but I still don't like the fact I can't use the adb shell. Typing characters on the G2 is a pain in the ass.
I still want to know why I can't enter superuser from the PC adb shell. Am I doing something incorrectly?
Thanks a lot for your help!

Try clearing data for the SuperUser app?

go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.

dietotherhythm said:
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
Click to expand...
Click to collapse
This worked perfectly! When I entered su from the command prompt, the SuperUser app popped up on the phone's side and I hit allow. It then let me through.
What exactly was broken though? Why did mounting everything from the Clockwork Recovery menu fix this?

reboot/reboot recovery doesnt work in terminal

im having trouble wirh "reboot recovery" command in my terminal/adb shell
when i try to run in terminal, i get "not permitted!"
and adb shell says [1] Segmentation fault reboot recovery
if i try running reboot -f in terminal or adb shell, i get "usage: reboot [-n] [-p] [rebootcommand]"
i've checked /system/bin, and the reboot bin is there
i've checked the permisssions, originally set to rwsr-sr-x
changing them to rwxr-xr-x makes no change
i found several threads with ppl having the same trouble:
http://forum.xda-developers.com/showpost.php?p=16022907&postcount=2040
http://forum.xda-developers.com/showthread.php?t=1280074
http://forum.xda-developers.com/showthread.php?t=935715
the only one i found useful is the 1st one
the only way i got reboot working is by deleting /system/bin/reboot, and using "reboot -f". without the -f switch nothing happens. if i do reboot recovery -f, it only rebots
but what i really want is to reboot into recovery. any idea on how to? i read in first linked post that the problem is in symlinked reboot to busybox, thats why deleting helped somewhat. anyone has an idea on how to get rebooting to recovery in terminal working?
oh, and my rom is rcmix 4.0. i've read that problem is rom related. but i dont want to switch, because it would defeat the purpouse in the first place....

You need an insecure boot img to run adb as root. No root no reboot. From terminal instead try sudo -i reboot recovery.

sudo not found
and i have root, i do get # in terminal and adb shell. adb commands like push/pull/chmod work fine
about insecure boot image, as far as i can understand you need that in order to have root, whuch i do have. and afaik, that means pretty much all custom kernels? if im missing something here, please do explane...

[Q] Nexus 4 - SU not working anymore but binary present

Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...

I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
skyraven83 said:
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
Click to expand...
Click to collapse

it seems in the end that it was all in xprivacy problem....
solved and now it is functional
skyraven83 said:
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
Click to expand...
Click to collapse

Just so you know
The reason you probably did not get responses to this is because you posted it in Galaxy Nexus section and not Nexus 4 forums