I'm having a problem rooting my Nexus One (I have also read the newbie FAQ and searched the forum to no avail) - I have followed the instructions listed on the androidandme site.
When I try to unlock using fastboot I get this returned:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFOErasing userdata...
FAILED (status read failed (Too many links))
When I start the phone in fastboot mode it now says *** UNLOCKED *** at the top of the screen. I then flashed Amon-Ra's recovery image, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-
RA-nexus-v1.6.2.img
sending 'recovery' (3954 KB)... OKAY
writing 'recovery'... OKAY
I assumed everything was going to be fine despite the issues unlocking. On trying to boot into recovery mode all I get is a screen with an exclamation mark and the android robot.
On turning the phone on as usual it seems that I can not run "Root required" apps such as the N1 torch.
I have tried running the OEM unlock command again but it seems to think that it has worked, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFODevice was already unlocked!
OKAY
It would seem from the newbie guide that I still need to flash the recovery image but that seems to be going fine. I can't see that I've messed up so far so is there some way to "unroot" my phone or go through the OEM unlock process again?
Thanks.
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
I tried this, but still don't have root permissions - any thoughts?
I have read and searched and read some more and searched some more, and now just need some help...
Thanks in advance.
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
jongie123 said:
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
Click to expand...
Click to collapse
I suggest One thing. Pay 15.47 american Usd, at Online Kitchen for Modaco, Viola, Your done, always rooted.. Always Su'd up..
The Bootloader is simple on a windows machine, and so is root.. On Modaco's site there is a whole tutorial on this.. Plus search the threads, a whole ish load too..
i"d pay the 15.47.. Just Nike it, Just do it.. It's so much easier.. Just click-click, bake, download, flash, done..
Go..Go..!
jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
If you just need root, get 'superboot'. It needs to be flashed to the "boot" partition (after unlocking the bootloader).
What it does is copy the root files to the data ROM and sets up permissions the first time the phone is booted (runs some sort of script I guess).
Link to superboot (free), make sure you get the right version:
http://android.modaco.com/content/g...erd79-epe54b-superboot-rooting-the-nexus-one/
look up "get root back".... Try these commands via ADB:
adb remount
adb shell chmod 6755 /system/xbin/su
....This should "fix_permision" and get you root back, IF you ever had it....
papermonk said:
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
Click to expand...
Click to collapse
Using adb you can issue "adb reboot recovery" and wind up in recovery mode. You can also hold down the power button and trackball (connected or disconnected from the computer) and enter fastboot. From there, select bootloader and then recovery.
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
sadhuKashmir said:
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
Click to expand...
Click to collapse
If you are rooting a G1, correct me if I am wrong, but couldn't you just use one of the one click root methods?
I thought all of the patches denying one click root were contained in official FW's of GB and the G1 did not get it.
Related
Alright, I give up.
I've wasted one full day and all I do is keep going in circles. I have an unlocked bootloader but I am not able to flash custom recovery to it. When I do:
fastboot flash recovery recovery-RA-passion-v2.2.1.img
it is successful but am having the problem mentioned here:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android)."
http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
So, no custom rom because I cant turn off verification in order to flash custom rom zip file. Now the problem is that I can't even fix this problem because I don't have root so I can't delete the following files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
When I try adb shell it keeps saying "permission denied"
It gets better - I've managed to mess things up royally even further. I tried flashing FRG83 system image using "flashboot update update.zip". It was successful but now my phone is going in boot loop!!
Can someone please help me before I lose hope in humanity?
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
You can either flash a pre-rooted GB, flash the su.zip and then you'll have su access to delete the files when in system or adb, or flash this zip which will remove the two files...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App
danger-rat said:
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
Click to expand...
Click to collapse
I totally did not know this. Thanks a lot buddy
hi there every one i updated my nexus one to 2.3.6 (GRK39F) from stock 2.3.4 (GRJ22) sorry but i did not read the post for to upgrade and keep root before upgrading to 2.3.6 and now i am suffering and thought it is not a good idea to post a question there so posting here
my problem is when i upgraded 2.3.6 i was rooted and had clockworkmod recovery image and i had a backup from rom manager as well but before upgrade i wiped the partition and cache and after upgrade i dont have SUPER USER permission nor the clockworkmod recovery tried to flash su.zip from sd card but no luck please can anyone help me get my root back pleaseeeee i need help ....
You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...
danger-rat said:
You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...
Click to expand...
Click to collapse
Thankyou very much danger-rat really appriciate your help but today was a bit lucky day for me
I tried to flash a recovery image through ADB and then it went well and then flashed the su.zip from sdcard that gave me superuser permission again thanks again for your help
@0mpranav
No need to flash the system partition, no need to use ADB, just flash Superboot:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759
jboxer said:
If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759
Click to expand...
Click to collapse
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
I have purchased two second hand Nexus Ones. The first thing I did after receiving them and charging the battery was to reboot into fastboot mode and issue "fastboot oem unlock" command. Since they were purchased second hadn I didn't thing I had a warranty anyway so unlocking the bootloader seemed to be a non brainer.
GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
Will any version of su.zip, and fastbook.zip work? What about recovery-RA-passion-v2.2.1.img? or should we be using a different version?
If we should be using different versions of those, could you link to where we could get them?
I've had my Nexus one half-rooted since 2.3 came out, and I haven't been able to root it back.
why mess with 2.3.6 just use oxygen 2.3.7...
kuljit55 said:
why mess with 2.3.6 just use oxygen 2.3.7...
Click to expand...
Click to collapse
I'm sorry I have no idea what that is. I don't even know if its helpful at all. Again, I don't even have root, or a custom recovery. Presently, I have an unlocked bootloader, ADB on my PC, and a half-rooted nexus one from before 2.3.
I have absolutely no idea how to do anything presently, and when someone tells me that trying to root on 2.3.6 is futile and to just use a custom update, it doesn't make any more sense to me.
Care to elaborate past one line that doesn't help at all? Hell when using shell commands through adb, it keeps on saying "permission denied" any time I type in su.
You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...
danger-rat said:
You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...
Click to expand...
Click to collapse
Thanks Danger-rat. Although I know you said nothing different that what was already said in this thread, I figured that since you didn't give me specific info about whether or not there were multiple versions of su.zip or fastboot.zip, I figured I should take that as a "No.", so I went for it. All re-rooted now.
I appreciate the help.
EDIT: So if you are as new to this stuff as I am, anyone else who's reading-
You can DL su.zip from http://www.google.com/url?sa=t&sour...ZxOuf9Kw_URvtvh9Q&sig2=Hj72LDNoiBq2Zoa4QquZWQ
and fastboot.zip from http://www.mediafire.com/?ttdkgamud3j
and amon Ra 2.2.1 from http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-passion-v2.2.1.img
then follow the directions here: http://forum.xda-developers.com/showthread.php?t=1019759
** Note: again, these are for people who have unlocked bootloaders. For that info, you'll have to go elsewhere, but it should be readily available, such as this stuff is. I'm just linking it again because I know how frustrating it can be for people like me who aren't too well versed in rooting/unlocking yet.
Downgrade 2.3.6 to 2.2.2 - Nexus One
Problem:
I would like to downgrade my Nexus One to 2.2.2, because I've had non-stop problems with Gingerbread.
So I've gone through the Bootloader -> Recovery -> apply sdcard:update.zip steps, and it fails. This begs the question, how do I go from 2.3.6 to 2.2.2?
Fix:
Generally, phone manufacturers will not allow you to downgrade for various reasons. The stock recovery does indeed validate the update image, so that it's of a greater (or same) version than the installed system. With the Nexus One being a developer phone, you can unlock the bootloader and replace the recovery image with the one that doesn't perform this check, and will allow installation of any image. The caveat is that unlocking the bootloader voids your warranty with the carrier (and sometimes the manufacturer too,) and wipes all user data off the device.
Unlocking the N1 is dead easy. Just install Android SDK and the USB drivers (located in "google-usb_driver" directory.) Then restart the phone in bootloader mode by shutting it off and powering on while holding down the trackball, hook it up to the computer via USB, and in command prompt issue the following command: C:\<path to Android SDK>\tools\fastboot oem unlock. You will be presented with a confirmation screen with further instructions. Upon successful unlock, you can flash a custom recovery that will allow you to install any custom ROM, including downgrade to 2.2.x stock version of Android OS.
To flash ClockworkMod recovery, download the latest version for Nexus One from here, reboot into bootloader mode (power on while holding the trackball down,) and in command prompt issue command C:\<path to ANdroid SDK>\tools\fastboot flash recovery C:\<path to downloaded img>\recovery-clockwork-3.0.0.5-passion.img
Reboot to bootloader mode again, and then use the Volume keys to highlight the "Recovery" option and press Power button. You are now in ClockworkMod recovery, and can flash any custom ROMs via the "Install zip from sdcard" option.
Here is a "stock" 2.2.2 ROM (with root) off XDA-developers forum.
http://forum.xda-developers.com/showthread.php?t=927935
source:http://android.stackexchange.com/questions/13933/downgrade-2-3-6-to-2-2-2-nexus-one
Try It & Report Back...
I want to return to stock Ive messed a few things up. Is there a RUU for 1.31?
?
Yeah, I second that request...
Reading through the forums, there isn't one released yet.
tbrad413 said:
I want to return to stock Ive messed a few things up. Is there a RUU for 1.31?
Click to expand...
Click to collapse
I realize this post is hard to follow and all over the place, but I'm tired.
Without a RUU:
Have ADB drivers ready to go if you don't already.
First be sure the bootloader is unlocked via HTCDev.
Next, get a copy of both TWRP and CWM recoveries, you can read why both at the end of the post.
Download the stock rom/stock rooted rom from the thread in development.
Plug the phone into USB and copy the rom onto the phone. Will most likely need to be in a folder called "0" in the root folder.
Open a shell and navigate to your copies of fastboot and adb from the HTCDev unlock.
"adb reboot-bootloader" "fastboot flash recovery TWRP.img"
This will flash TWRP, make sure that you change TWRP.img to the actual file name.
If TWRP doesn't work (like mine didn't), no big deal. Issue the following commands:
"adb reboot-bootloader" "fastboot flash recovery CWM.img"
This will flash clockwork mod recovery, which worked better for me than TWRP.
After you figure out which recovery you want, wipe data/factory reset.
Navigate to 0 and select the stock rom that you downloaded.
One of the recoveries will only see the "0" folder, it's a bug. I believe if you're on TWRP, you can only access 0 which is why you need to put the rom there. Clockworkmod should be able to see anything, but if I remember correctly immediately reboots with the latest firmware.
Flash the room and reboot.
That's how you can go back to stock without a RUU. All of this is from memory but it's accurate. The other option would be to S-OFF via revone and downgrade afterwards. You CAN use revone on the newest firmware - I did it earlier.
Good luck and all that jazz.
Why both recoveries:
TWRP ****ed up really hard on 1.29.x for me and failed to flash or see any files. CWM worked for me on 1.29.x but instantly reboots on 1.31.x. TWRP works for me on 1.31.x but can only see within /sdcard/0/, meaning nothing outside that 0 folder is flashable.
Other notes:
There's also some **** about USB-OTG but I didn't mess around with that. I've been working with multiple Ones over the passed few days and the steps above worked for me. I realize this post is hard to follow and all over the place, but this is all I've been doing this past week and I've got a lot of info on it.
Another note:
If you don't have a working install on the phone to boot into, you can do what I did and boot into the bootloader and use
adb push file.zip /sdcard/0/
Then boot into the recovery and it should be installable.
Is it possible to gain root (on an unlocked + S-OFF device), without flashing a custom recovery?
I've been searching for a couple of hours, but couldn't find a working solution.
The superboot method doesn't seem to be working, something to do with not being able to boot into an image from fastboot anymore (I'm on the latest firmware/hboot).
Any other methods available?
Thanks in advance.
totoguy said:
Is it possible to gain root (on an unlocked + S-OFF device), without flashing a custom recovery?
I've been searching for a couple of hours, but couldn't find a working solution.
The superboot method doesn't seem to be working, something to do with not being able to boot into an image from fastboot anymore (I'm on the latest firmware/hboot).
Any other methods available?
Thanks in advance.
Click to expand...
Click to collapse
If you want to use superboot then use an hBoot of 1.44. other then that you have to flash a custom recovery
These directions are based on Win7 pc...Assuming you have ADB, drivers and fastboot on your machine:
You need a recovery to use temporarily. Download (to your computer) the one you like and proceed:
Reboot phone to bootloader, enter fastboot
The next step temporarily boots your phone to a recovery. On a command prompt, CD to the directory where you downloaded the recovery image, then enter this:
fastboot boot "recovery.img"
You need to replace "recovery.img" with the file name of your choice that you downloaded: CWM or TWRP...also, do not use "quotes"
You should be in CWM or TWRP now.
Backup your phone with the recovery's nandroid...DO IT.
All you need to do is select the option to reboot. When you do, the recovery will ask you if you want to install root. Select "Yes" and you're basically done.
When you phone reboots, it will maintain the stock recovery and you'll have su in system/bin as well as the superuser apk in system/app. Now install busybox from the play store.
oophlamer said:
fastboot boot "recovery.img"
Click to expand...
Click to collapse
I've tried that with the superboot method, and it looks like it's not working anymore with the latest stock rom (or might be a 4.3 change). It just hangs and the phone freezes, until I hard reset with the power button.
I did another search now and it seems that the command might have been replaced with "fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img", at least on the Nexus 4.
I'll look into it when I get back home.
totoguy said:
I've tried that with the superboot method, and it looks like it's not working anymore with the latest stock rom (or might be a 4.3 change). It just hangs and the phone freezes, until I hard reset with the power button.
I did another search now and it seems that the command might have been replaced with "fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img", at least on the Nexus 4.
I'll look into it when I get back home.
Click to expand...
Click to collapse
"fastboot boot ..." no longer works as of hboot 1.54+, it used to work on hboot 1.44.
nkk71 said:
"fastboot boot ..." no longer works as of hboot 1.54+, it used to work on hboot 1.44.
Click to expand...
Click to collapse
Exactly what i was going to reply. I had tested this on my stock Hboot 1.54 to keep a 1:1 backup but failed miserably.
I have the same problem...
Any solution?
Not really sure what I'm doing wrong. Last rooted phone was a Nexus 5, and that was of course painless to root and flash ROMs to...
I'm using a Verizon XT1096 with 5.1 on T-Mobile.
So I was able to get the bootloader unlocked via Motorola's website, now that Verizon is allowing them to do so. No problems there. My problem now is that I can flash a recovery, but if it reboots, the recovery is gone. And I can't get any recoveries to flash anything. I can't push an apk, root zip, or even a ROM. Says Installation Aborted, with no other error codes. Even tried CWM and disabling Signature Checking, which gives me more info, saying that the footer is mismatched. Phone does say the bootloader is unlocked though so that shouldn't be it...
Honestly, I'd just like to get it on CM12 until I can get a Nexus 6P.. Can anyone tell me if I'm doing something wrong? Or is there just no way to root yet? I figured even the XT1095 CF-Auto-Root method would work for 5.1, but no dice..
Not sure what to do here. Please move my thread if need be. Don't post here much...
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
RepeatUntilTheEnd said:
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I thought I tried that but maybe not. I've read that some stock ROMs can and will overwrite the recovery upon booting, but I could be wrong. I'll look at that when I get home tonight.
oraixearl said:
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
Click to expand...
Click to collapse
Thank you, I'll try this tonight when I get home. This may solve it. I think I remember the bootloader spitting something out about a partition mismatch.. Will report back as soon as I try it.
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
TsarProdigy said:
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
Click to expand...
Click to collapse
Strange as it worked for me. I'm glad you got it sorted out tho. Cheers.