I went back to a factory image from frf50 this morning, then upgraded all the way back up to FRF83. I still have my unlocked bootloader. I ran the superboot file for FRF83. Looked good.
When I adb shell I now get "#" but cannot recognize the command "su".
I can't get titanium back up or quickboot to recognize root. I remember a new superuser.apk fixed this on a mytouch.
Any suggestions for getting full root permissions.
Related
I just traded up from an iPhone 3G to a Europe model Nexus One and am considering rooting for unrestricted access to the App Market (I am using in China), but I wanted to make sure that I've got all my facts straight about the rooting process. My bootloader is unlocked and I have flashed upgrade packages manually before, but everything else appears to be stock.
So first, root access actually only involves installing the Superboot update over the stock ROM, if there is a superboot for that ROM version, right?
This then lets you install apps that require root access (such as Market Enabler or MarketAccess), so if I just wanted unrestricted market access, then this is all that I would have to do, right?
However, getting root also lets me install a custom recovery, which gives me some nifty functions from the recovery boot, such as backing up my phone (does it do anything else? Why does Amon_RA's recovery have Busybox if it already comes with superboot?). It also allows me to install a custom ROM.
So far so good? Am I missing anything?
Are there any other methods to root? I have heard that you can install the SDK and go through ADB to manually do root, but I have not found any detailed information about this method. I have FRF91 OTA, and since there is no superboot for that yet, could I potentially got the ADB route?
Didn't miss anything.
You can go several ways: since your bootloader is unlocked, to save yourself the pain with ADB loop method, which is completely unneeded, you can just use the regular method, skipping the "unlock bootloader" part, which leaves you with "flash custom recovery" part (totally independent) and then just flash whatever ROM you like, pre-rooted. You don't need to flash a rooting file over your ROM, you just can change your ROM to pre-rooted one.
So you are saying that I can flash a custom recovery, then load a custom rom that is pre-rooted?
How do I flash a custom recovery if I am not rooted? I thought that in order to get the recovery you needed to root via superboot?
And I must have a custom recovery in order to have a pre-rooted rom, otherwise the phone will reject the package, right?
So the only thing that prevents root on the Android is the rom and recovery partition's own integrity check for whatever you are flashing? In other words, people can lose root by flashing a stock rom, and you can get root by flashing a pre-rooted rom. I seem to remember seeing some pre-rooted packages saying that you must have previously had root in order for it to work. Is that not correct, then?
Thanks.
hgcrpd said:
I just traded up from an iPhone 3G to a Europe model Nexus One and am considering rooting for unrestricted access to the App Market (I am using in China), but I wanted to make sure that I've got all my facts straight about the rooting process. My bootloader is unlocked and I have flashed upgrade packages manually before, but everything else appears to be stock.
So first, root access actually only involves installing the Superboot update over the stock ROM, if there is a superboot for that ROM version, right?
Click to expand...
Click to collapse
Not exactly - root access simply indicates having the su and superuser.apk binaries installed, and the suid bit set on su. But you are close enough. If you are running FroYo, Cyanogen and Lox have published flashable rooters.
You will already need a custom recovery to flash either of these - but since your bootloader is unlocked, a custom recovery does not pose any problem - see below...
hgcrpd said:
This then lets you install apps that require root access (such as Market Enabler or MarketAccess), so if I just wanted unrestricted market access, then this is all that I would have to do, right?
Click to expand...
Click to collapse
Yes.
hgcrpd said:
However, getting root also lets me install a custom recovery, which gives me some nifty functions from the recovery boot, such as backing up my phone (does it do anything else? Why does Amon_RA's recovery have Busybox if it already comes with superboot?). It also allows me to install a custom ROM.
Click to expand...
Click to collapse
Couple of points here:
1. No, you don't need root to install a custom recovery - you need an unlocked bootloader. In fact, you have reversed them - you usually need a custom recovery to get root! Since you have that bootloader already unlocked, you can go ahead and install Amon's recovery (or another one) and get what you need to get.
2. Recovery does not use the same shell and variables as /system. Busybox is usually installed in recovery to allow you to run things via ADB or scripts when in recovery mode without manually calling them off of system (something that would be a problem if you were formatting and rewriting system, for example).
hgcrpd said:
Are there any other methods to root? I have heard that you can install the SDK and go through ADB to manually do root, but I have not found any detailed information about this method. I have FRF91 OTA, and since there is no superboot for that yet, could I potentially got the ADB route?
Click to expand...
Click to collapse
You need to have the SDK installed (which includes adb) to unlock the bootloader in any case, right? Or did someone unlock the bootloader for you? In any case, I would just install the SDK - it's free, fast and gives you access to fastboot and adb. You need fastboot to install a custom recovery, and adb is useful for lots of things.
And there are plenty flashable root zips for FRF91. You need to first install a custom recovery!
http://forum.xda-developers.com/showthread.php?t=715799
http://forum.xda-developers.com/showthread.php?t=686627
So, if I were you:
1. Install the Android SDK on your computer to get ADB, fastboot and the necessary drivers.
2. Download and flash a custom recovery using fastboot.
3. Reboot into recovery.
4. Copy Lox or Cyan's rooter to your SD card using adb push.
5. On the phone, in recovery, do a nandroid backup!
6. Flash the zip from step 4.
7. Reboot your phone and confirm that you have root - the easiest way is to start up a terminal session and type "su". The Superuser authorization program should pop up and ask you to approve the application's request for root access. Grant it. If the prompt turns from "$" to "#", you have root.
1. No, you don't need root to install a custom recovery - you need an unlocked bootloader. In fact, you have reversed them - you usually need a custom recovery to get root! Since you have that bootloader already unlocked, you can go ahead and install Amon's recovery (or another one) and get what you need to get.
Click to expand...
Click to collapse
I see. So the post on modaco is not quite correct when it says that root is a pre-req for Amon_RA's recovery. I'm guessing that's only a pre-req if you flash via a terminal session on the phone? (By the way, is there an official terminal app? The only one I could find was Terminal Emulator.)
You need to have the SDK installed (which includes adb) to unlock the bootloader in any case, right? Or did someone unlock the bootloader for you?
Click to expand...
Click to collapse
Bootloader was unlocked when I bought it. The phone is a grey-market item that I purchased here in China, and every grey-market phone that comes in gets modified by the importers in order to add Chinese language support and such. I think that's all they did, since I've been able to do updates and get OTA without a problem.
Thanks! I will give the SDK route a try, if I get time before the superboot for FRF91 comes out.
I dont know why but it seems like im the only person in the world who cant get his phone to work properly.
I rooted, got amonra recovery 1.7.0, partitioned ext2/swap/fat32, flashed newest radio, then flashed dangerspl.
And any rom I flash will never boot past the G1 logo screen.
I have only gotten jesusfreke's 1.5v2 rom to flash. it was the first rom i tried.
i rooted by doing the guide in "forum.xda-developers.com/showthread.php?t=548924", which asks me to go to g1upgrade.com and install root.apk, then use the telnetd method, and then protect root. to confirm i have root, when i go into terminal emulator, and use su root, it asks me if i want to allow application to run as root:root.
any attempt at getting a logcat using adb just says /sbin/sh: logcat not found.
it seems like everything i do always ends in an error noone understands.
can someone please help me before i give up on android forever?
Tatta_ram said:
I dont know why but it seems like im the only person in the world who cant get his phone to work properly.
I rooted, got amonra recovery 1.7.0, partitioned ext2/swap/fat32, flashed newest radio, then flashed dangerspl.
And any rom I flash will never boot past the G1 logo screen.
I have only gotten jesusfreke's 1.5v2 rom to flash. it was the first rom i tried.
i rooted by doing the guide in "forum.xda-developers.com/showthread.php?t=548924", which asks me to go to g1upgrade.com and install root.apk, then use the telnetd method, and then protect root. to confirm i have root, when i go into terminal emulator, and use su root, it asks me if i want to allow application to run as root:root.
any attempt at getting a logcat using adb just says /sbin/sh: logcat not found.
it seems like everything i do always ends in an error noone understands.
can someone please help me before i give up on android forever?
Click to expand...
Click to collapse
when it ask for allow root check remember and hit always
have you booted in bootloader to see if you have latest radio and SPL
what radio did you flash?
and what rom are you trying to flash..
How long have you waited on the g1 screen?
Hi guys, i've recently bought 2 Milestones (A853) with software issues (both for US$30) and decided to flash some roms. both units are 90.78 BL,
but one was on eclair while the other was on froyo.
the eclair one is now running CM7, the process of flashing the vulnerable recovery went fine.
the other one...
when it boots on the recovery, it stays on the ! triangle and doesn't matter which buttons i press its doesn't shows me the menu itens... i don't think that was a problem with the buttons, since the day it arrived i went to recovery and wiped...
there's any sort of incompatibility of the updated 2.2 and the vulnerable recovery? it's ok to flash a 2.1 sbf now?
there's something i could do using adb? reboot recovery only goes to the same screen... there's a way to start a update.zip flash from adb?
thanks!
The latest official update should be fully compatible with the vulnerable recovery method.
Try flashing a 2.1 sbf, check all hardware keys for functionality and try again.
well i think my camera button is to blame.
but searching (thru google) i came to this topic here on xda:
http://forum.xda-developers.com/showthread.php?t=1833992 that teached me how to start an update.zip
one of the issues is that 2.2 was an OTA so it had install-recovery.sh flashing a non vulnerable recovery on every start
flashed a retail eclair sbf then a flashed vulnerable recovery sbf and let the system boot normally. Had it rooted and went superuser on terminal thru adb shell (don't know if it is important to be su, when i ended that i noticed that i was su)
you should have already on the root of SDCARD Openrecovery folder and the update.zip of OR
Code:
su
# mkdir /cache/recovery
# echo "--update_package=SDCARD:update.zip"> /cache/recovery/command
#reboot recovery
after the last line milestone will be down and boot in recovery and start updating.
hope that helps someone with issues on the recovery menu, that does nothing except showing the Yield sign or phones with dead buttons...
where i need to use those codes?
you use on ADB thing?
or some other program?
or on the phone?
tks! ^^
using adb...
activated USB debugging on settings, then on computer went to adb shell.
Ok I got my phone new in July and fully converted it to the google play edition successfully. I rooted it as well and had no problems. Eventually the OTA for 4.3 came out and I lost root. I successfully got it back using superuser (clockworkmod version). After that the JWR66Y update came out in august or september. I didn't lose root on that OTA. Now my problem:
Last night I wanted to switch from superuser to supersu. I installed supersu from the play store. Supersu said it needed to update supersu so I let it. It failed. I then downloaded the latest clockwork recovery (6.0.43), flashed it and then tried to install UPDATE-SuperSU1.6.5.zip. No errors of any kind came up. I then rebooted the phone and I had no root. No superuser app and no supersu app. Running su from android terminal emulator causes the shell to hang.
I then booted back in to recovery and connected my phone to my mac. Ran adb shell and cleaned out all of the su crap. /system/xbin/su /system/bin/su /system/app/superuser.apk /system/app/supersu* /data/app/eu.blahblah.supersu.apk /system/xbin/daemonsu
After I did that I wanted to see if TWRP would work better. I flashed that (latest one from their site) and then tried to install the supersu zip again. Same thing as before with CWM.
Booted back in to recovery once again and manually deleted all of the su crap. I then tried to flash the zip flashable version of superuser (clockworkmod's). After I installed the zip then rebooted I got a message saying su needs to update. I try to update it and it fails.
So I really need to get root back. I don't care if its superuser or supersu or something else. Someone please help me with this. I'm completely stumped on the issue.
Thank you
Edit: missed deleting 3 files from /system/etc.
.has_su_daemon
.installed_su_daemon
instal-recovery.sh
Once I deleted those and reinstalled superuser.zip everything works now.
I just picked up a Nexus 6 to give Project Fi a shot. I figure I might as well root it before setting up all my apps and whatnot. I'm using the Nexus Root Toolkit 2.1.9 and am having some issues. I have all the drivers installed and set up correctly but I can only seem to get ADB to recognize the phone if I change the USB option to Transfer Photos (PTP). During the root process the phone temporarily boots to TWRP and it's at this point where NRT loses ADB recognition and won't finish rooting. Is there something else that I'm overlooking?
You own a Nexus, take 5 minutes to learn ADB and fastboot commands and you don't need a toolkit. To root it, all you should have to do is flash SuperSU in TWRP. But if you used some stupid toolkit to install TWRP, who knows if it worked right or is the most up to date version.
Get the latest version of TWRP (twrp-3.0.3-0-shamu.img) from here and flash it by using "fastboot flash recovery twrp-3.0.3-0-shamu.img" then reboot into TWRP, drag the SuperSU SR3 zip onto your phones storage (you can either do this from in TWRP or from normal Android), flash it and reboot. Boom, you have root.
I'm definitely no stranger to ADB and Fastboot as I've owned other Nexus devices in the past put it's been a few years. I already had NRT installed so I just went that route out of laziness lol. Thanks for the links to the latest SU and TWRP. I'll flash 'em the old fashioned way.
I ran into the same issue with NRT, but to get it to root, I just gave TWRP a password when it asked to mount (it won't do anything anyway..fail to mount), then when asked whether to "Keep System Read only", I clicked the "Never show this screen during boot again" checkbox, then swiped to allow the modification to the system partition, which will then bypass that query when it goes back to TWRP to complete the root script. I hope this helps someone in the future.
By the way, I flashed N6F26R before the root.