Database Users

Root Nexus One on a Mac/Linux/Windows

Hi guys. I published a step by step guide for all the newbies (I had a tough time the first time. Slightly different combination but it works! Also flashed the custom recovery image!
http://ilikemygooglephone.com/2010/...-and-root-google-nexus-one-mac-windows-linux/

This tutorial on rooting and flashing the RA recovery rom is THE BOMB!
Followed all the steps and now I too have gone to the dark side, and eaten some cookies....
Nice work.

Great! Love it!

This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.

Does it have to be 2.0.0? or can it be any of the RA recoveries above 2.0.0?

bahathir said:
This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.
Click to expand...
Click to collapse
A question for you, if it's possible to simply just change the permission of the su file on the phone, why do most auto root zip's come with an su file of their own?
Could they not just run the script above?

this whole procedure thing ... do stock users like myself lose anything? Like, does it wipe data or does it simply root and nothing at all changes?
You can never tell with these procedures... half wipe the phone...

I haven't tested it, but from the steps listed above (by bahathir) you won't lose any data.
All he's doing is getting you to boot into fastboot mode (power on the phone while pressing the trackball), and then loading the custom recover into temporary memory.
Then, the system folder is mounted and the required permissions are applied to the su file. Once that's done, you reboot your phone and nothing else changes.
The question that I had above though, is that I've not seen this method used before. Most one-click root methond replace the su file (requiring you to flash a zip file from custom recovery).

ahh too bad it doesn't work. maybe a 2.3.3 thing, but I just tried unlocking my bootloader and it says I'm missing AdbWinApi.dll from my PC ... but it's clearly there.
I have the most up-to-date Android SDK packages. I've used them before to root my nexus without a hitch...

SU should be present on the system, and the method above takes it for granted. Thus it's for RErooting. Rooting methods bring the SU - they don't care if there's one on the system, assuming that there isn't.
On the other hand, I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader. If it's the case - this is the most overlooked and bulletproof rooting method for Nexus. But I doubt it's the case.

Here's a n00b question. I have an unlocked boot loader and had previously rooted my phone using superoneclick. I wiped all the data before moving to stock gingerbread since I was on CM7 nightlies before. So there is no "su" in my phone. I get the obvious error:
c:\android-sdk-windows\platform-tools>adb shell 'chmod 4755 /system/bin/su'
/sbin/sh: chmod 4755 /system/bin/su: not found
when I try to run the steps listed here. Any ideas how to get the 'su' on my phone?

I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.

Jack_R1 said:
I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.
Click to expand...
Click to collapse
Thanks Jack! Can you point me to an su package that I can safely flash with gingerbread?
Sent from my Nexus One using XDA App

I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?

aliezad said:
I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?
Click to expand...
Click to collapse
I don't think that zip would work.
I rooted by applying the su.zip provide by dsixda here: http://forum.xda-developers.com/showthread.php?t=968396 (attachment, bottom of first post)
You would need to flash this from custom recovery (I used Amon RA 2+).

Thanks Brownbay! Worked like a charm!

Jack_R1 said:
...I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader.
Click to expand...
Click to collapse
Unfortunately this won't work on a locked bootloader (at least, not on mine!), so if you've used 'super one click' to root your N1 without unlocking it (like me), this method won't work for you.

I already have had my bootloader unlocked. I'm wondering if this rooting method alone will wipe my phone?

No, it won't wipe your phone.

HTC Desire HD won't boot after flash

Hello!
I have a big problem.
I might have bricked the device however the things what i can do are the following:
- Boot into recovery (clockworkmod)
- start a usb data connection with a computer (clockworkmod)
- input of the ADB commands through terminal running in the computer
What i did?
Flashed the memory with a Cyanogenmod 6.3 according to official guideline:
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide
and took note and used most procedures from there actually:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Didn't do the engineering hboot.
Everything was working. I got cyanogenmod working.
Then after a while i tried to restore a backup which i had from original HTC configuration which was actually just before i did the cyanogenmod flash with clockworkmod.
So the backup was from the time i already unlocked the phone from locks and had root access.
So again the restore function worked and everything was back to normal.
How i managed to half brick the device?
Yesterday i wanted to put cyanogenmod back to my phone and then the s hit happened.
I admit that i didn't check whether the locks were off i just thought that these should have been off because backup soft was from time i had phone unlocked.
Anyway to cut the long story short - after flashing the memory with cyanogenmod with the help of rom manager the phone didn't boot anymore.
I tried all the options from clockworkmod flash and format and upgrade straight from sd card a new cyanogenmod but nothing worked. Again the white HTC screen and connection through a usb cable.
So probably i have the s-off and who knows what else.
I dont have a root access anymore as well because i already tried it through the terminal. It doesn't recognize the su command.
Question is, how can i put the cyanogenmod back on by only using clockworkmod recovery and working ADB connection through usb link?
Probably have to just get the locks off but the original instructions say i have to have terminal emulator running in phone but i only have clockworkmod recovery soft running at best.
S hit, again very long story, but hope someone can help me!
Cheers!

I had a similar problem yesterday, after flashing ClockwordkMod Recovery to version 3.0.0.5 (it said it had an update) and trying to reinstall CyanoGenmod 6.3 my phone would no longer boot, it got stuck in the white HTC Logo screen.
I'm not really an expert on this stuff, but I managed to "recover" my device by downgrading it again to 1.32.405.6 using this thread: http://forum.xda-developers.com/showthread.php?t=905003. First I had tried to recover a previously backed-up ROM, but that did not work.
I had to put the stock 1.32 PD98IMG.zip file on my SD card using ClockwordMod Recovery (since I could no longer boot), I'm not exactly sure which steps I took to do so, I have tried a lot of things yesterday before I got everything working again.
After this my phone could boot again and I was ready to play around again. I reinstalled CyanogenMod again using an older version of ClockwordMod Recovery. I'm not sure if this is related in any way, but my phone works smooth again..
Once again; I'm really not on expert on how all this stuffs works, I just hope that I can help you on the way with some ideas on how to fix your device.
So probably i have the s-off and who knows what else.
Click to expand...
Click to collapse
I figured out wether my device was S-OFF and/or Eng S-OFF by entering "adb reboot bootloader" from cmd. At the top of the page for me it states:
ACE PVT ENG S-OFF
I believe it stated only SHIP S-OFF when I had the problems you describe.

Thanks man for quick reply!
I definitely try the downgrading solution and i remember i too did the update for clockworkmod rom manager before the flash.
I'll report back tomorrow.
Cheers!

couldn't boot up any roms earlier after upgrading clockworkmod recovery to v3... downgraded to 2.5.1.3 and worked fine

Hi Guys, I have exactly the same problem. It would be really great if you provide me the step by step process to downgrade clockworkmod recovery.
Cheers,
Pav

I'd like to say to you guys that the downgrading solution worked
Didn't have to use any programs inside phone except clocworkmod recovery which was the only thing i had running.
Thank you user jvdminne!
The downgrading solution was in official cyanogenmod guidelines as well but forgot it anyway.
------------
Pavanka!
The downgrading solution from the link is pretty step by step actually.
But anyway, with my half-broken phone the lines didnt do the trick:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
I had to copy psneuter and misc_version to /tmp folder not into /data/local/tmp.
But anyhow, i already had # root access through computer. Probably from last half flashed system.
So only thing i basically had to do was to cd in windows cmd into folder where i had psneuter and misc_version and after that:
Code:
adb push misc_version /tmp
adb shell chmod 777 /tmp/misc_version
adb shell
in the shell (adb shell):
Code:
cd /tmp
./misc_version -s 1.31.405.6
And after that follow the instructions from previous link.
To get the ADB functions working just follow the guide here or from previous link where it had adb program included, but not sure whether it was working cause i had it from Android SDK package already set.
Hope you got some sense out of it.
Cheers!

Hey
I had similar problems to those mentioned in the beginning with the cyanogen mod...
I installed cyanogen and the it got to the screen with the blue swirlyness and then just kept restarting. I decided to restore a backup and just got stuck on the white htc screen.
I decided to follow this post and now am stuck with this...
I just tried a couple of different things to no avail...

maxa1577 said:
Hey
I had similar problems to those mentioned in the beginning with the cyanogen mod...
I installed cyanogen and the it got to the screen with the blue swirlyness and then just kept restarting. I decided to restore a backup and just got stuck on the white htc screen.
I decided to follow this post and now am stuck with this...
I just tried a couple of different things to no avail...
Click to expand...
Click to collapse
If you had ROOT , S-OFF etc you shouldn't need to go through all this rigmarole, if you can access recovery carry out a full wipe /system /cache /dalvik-cache and reflash your chosen ROM, should be all that's required

ghostofcain said:
If you had ROOT , S-OFF etc you shouldn't need to go through all this rigmarole, if you can access recovery carry out a full wipe /system /cache /dalvik-cache and reflash your chosen ROM, should be all that's required
Click to expand...
Click to collapse
phew cheers for that. First time flashing and I thought I killed me poor desire.

Cannot root 4.1.2

After I got my new nexus, I decided to root it. I used mskips toolkit with 4.1 and it worked like a beaut. But I can't for the life of me root 4.1.2.
Checklist:
Downloaded the drivers succesfully
Can enter ADB succesfully. Under device manager it says "Google Nexus 7 ADB interface"
Tried WugFresh's toolkit
Unlocked bootloader
Tried installing custom recovery (see below)
(Checklist to know what I have done, for people to help me and future people with problems)
The reason adding CWM or TWRP doesn't work is because the device can't be rooted. You need to be rooted to change recovery file names, and whenever I boot recovery, I get the dead android and a red ! (stock recovery).
When it sees if busybox is installed, and sends the command, it comes back negative.

I'm having the exact same problem -- generating the same set of error messages as you show at the top of your screen capture. I bought a new Nexus 7 32GB and updated it to 4.1.2 before trying to root it. At the time I hadn't read anything that told me this might be a bad idea. I figured -- update to the latest version then root it. I've tried changing how I have it connected (media or camera), what USB port I connect to, what USB cable I use, which boot options I select -- NOTHING makes a difference. I have gotten my bootloader to unlock, or so it seems, as I've got the unlocked padlock image during boot up. But I'm totally stuck on how to proceed to get root.

lesdense said:
I'm having the exact same problem -- generating the same set of error messages as you show at the top of your screen capture. I bought a new Nexus 7 32GB and updated it to 4.1.2 before trying to root it. At the time I hadn't read anything that told me this might be a bad idea. I figured -- update to the latest version then root it. I've tried changing how I have it connected (media or camera), what USB port I connect to, what USB cable I use, which boot options I select -- NOTHING makes a difference. I have gotten my bootloader to unlock, or so it seems, as I've got the unlocked padlock image during boot up. But I'm totally stuck on how to proceed to get root.
Click to expand...
Click to collapse
When you run wugs toolkit to root, does it reboot your nexus? I have not rooted a 32GB yet but I have done a 16GB on 4.1.2 factory image without any problems.

There is nothing different between rooting an 8/16GB unit versus the 32GB ones. Nor does 4.1.1 or 4.1.2 matter.
I bought a 32GB one a few days ago, upgraded to 4.1.2, and had the bootloader unlocked, custom recovery installed and device rooted in about 5 minutes.
The issues you are having are why I hate these "toolkits". They don't always work properly, and when they fail, the user has no idea what's going on. It's much better for people to actually perform the steps manually so that they understand what's going on behind the scenes. Because when you understand, you can better troubleshoot problems.
Based on the errors, it looks like the toolkit failed to remount /system as writable. As such, it couldn't push the APKs for superuser, nor make the su binary suid root. Which of course would break the rest of the install script.
It's a very simply process and doesn't need a toolkit. Use the android development toolkit tools adb and fastboot.
1) adb reboot bootloader
2) fastboot oem unlock
(select yes on tablet)
3) fastboot reboot-bootloader
(confirm bootloader is unlocked)
4) fastboot erase recovery
5) fastboot flash recovery <recovery.img>
(recovery.img should be a downloaded custom recovery file - CWM or TWRP, your choice).
6) Reboot into recovery
7) adb push <superuser.zip> /sdcard/superuser.zip
(superuser.zip should be whatever recovery flashable 'root' zip you want to use).
8) Using recovery, flash the zip file.
9) Reboot
10) Done.

phonic said:
There is nothing different between rooting an 8/16GB unit versus the 32GB ones. Nor does 4.1.1 or 4.1.2 matter.
I bought a 32GB one a few days ago, upgraded to 4.1.2, and had the bootloader unlocked, custom recovery installed and device rooted in about 5 minutes.
The issues you are having are why I hate these "toolkits". They don't always work properly, and when they fail, the user has no idea what's going on. It's much better for people to actually perform the steps manually so that they understand what's going on behind the scenes. Because when you understand, you can better troubleshoot problems.
Based on the errors, it looks like the toolkit failed to remount /system as writable. As such, it couldn't push the APKs for superuser, nor make the su binary suid root. Which of course would break the rest of the install script.
It's a very simply process and doesn't need a toolkit. Use the android development toolkit tools adb and fastboot.
1) adb reboot bootloader
2) fastboot oem unlock
(select yes on tablet)
3) fastboot reboot-bootloader
(confirm bootloader is unlocked)
4) fastboot erase recovery
5) fastboot flash recovery <recovery.img>
(recovery.img should be a downloaded custom recovery file - CWM or TWRP, your choice).
6) Reboot into recovery
7) adb push <superuser.zip> /sdcard/superuser.zip
(superuser.zip should be whatever recovery flashable 'root' zip you want to use).
8) Using recovery, flash the zip file.
9) Reboot
10) Done.
Click to expand...
Click to collapse
I agree with you, the problem of the tool kits, I experimented two of then
M, is that you are lost when something don't work, I lost hours and hours before understand it and do it by myself for 50 per cent .
Now that everything is good, I am very prudent with theses helpers,:good:

It's possible to flash without LCDscreen?

Hi. My normal screen just been destroyed, and it's not a big problem 'cause I normally use the EPD screen for everything, but I need it for flashing, backuping or restoring ROMs. Even for a factory reset I need the LCD screen for the first start configuration.
There is a way to do it just using the eInk screen? As long I know, adb can't do that. Maybe just fastboot with his partition-by-partition backup can do that, but don't know how to do it.
I am wrong with the impossibility for doing that with adb?
Thanks

Still in this quest...
I reafirm myself in the impossibility of flashing with adb (as I think for sideloading you need a custom recovery). I tried with "fastboot -w update xxxx.zip" with the full FOTA of android 6 RU version, and it came to me the error of missing android-info.txt and android-product.txt. I think about getting them from another ROM for yotaphone2, but prefer to ask you before.
The other option is to flash every single partition with fastboot, which is easy, but I have to manage how to do it with the format that my FOTA has.

eReader Fan said:
Hi.
Click to expand...
Click to collapse
I think you are looking for the most difficult ways and are unlikely to find them,It's easier to get a new screen.

Sure, but a lot more expensive.
It is a long quest since I started, but I think I almost did it!!!

It will be nice if you achieve it to post a tutorial
I got same problem, or just didn't thought about that till I restored the phone and realised what I did!!

It should be possible to make the phone usable.
Seeing recovery on the back screen will never be possible I think unless a skilled person puts tons of work into making that work, but you don't really need it.
I found that you can skip the initial setup by manipulating the /system/build.prop.
So if you can get an adb shell with the system partition mounted writable, then you can edit the file to skip the setup which should make it possible to immediately use the mirroring mode....
Getting an abd shell should be possible by first going into fastboot mode(using power+voldown) and then booting twrp recovery ( https://forum.xda-developers.com/yotaphone-one/development/twrp-3-0-2-0-yotaphone-2-t3494023)
Code:
fastboot boot twrpimg.img
Then wait a little until twrp is booted (just wait for a minute)
then open an adb shell:
Code:
adb shell
then mount the system in writable mode and add the setup skip line to the build prop:
Code:
mount -rw system
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
and then reboot (still in adb shell):
Code:
reboot
I tested that you can go into twrp and mount the system writable but since I don't wanna reset my device, I cannot say for 100% sure that you will then be able to immediately use mirroring mode!
Also, for this to work, i think your bootloader needs to be unlocked. You can also do that using fastboot, but there is a next step which pops up on the normal screen, but it either just pressing power-button to confirm or pressing voldown of volup first and then pressing power to confirm you wanna unlock, so no touchscreen interaction needed. Beware that unlocking the bootloader erases userdata!
Lastly, you need to have fastboot and adb installed, go xda and google if you are not familiar enough with that.
Greets and good luck

tomgaga said:
It should be possible to make the phone usable.
Seeing recovery on the back screen will never be possible I think unless a skilled person puts tons of work into making that work, but you don't really need it.
I found that you can skip the initial setup by manipulating the /system/build.prop.
So if you can get an adb shell with the system partition mounted writable, then you can edit the file to skip the setup which should make it possible to immediately use the mirroring mode....
Getting an abd shell should be possible by first going into fastboot mode(using power+voldown) and then booting twrp recovery ( https://forum.xda-developers.com/yotaphone-one/development/twrp-3-0-2-0-yotaphone-2-t3494023)
Code:
fastboot boot twrpimg.img
Then wait a little until twrp is booted (just wait for a minute)
then open an adb shell:
Code:
adb shell
then mount the system in writable mode and add the setup skip line to the build prop:
Code:
mount -rw system
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
and then reboot (still in adb shell):
Code:
reboot
I tested that you can go into twrp and mount the system writable but since I don't wanna reset my device, I cannot say for 100% sure that you will then be able to immediately use mirroring mode!
Also, for this to work, i think your bootloader needs to be unlocked. You can also do that using fastboot, but there is a next step which pops up on the normal screen, but it either just pressing power-button to confirm or pressing voldown of volup first and then pressing power to confirm you wanna unlock, so no touchscreen interaction needed. Beware that unlocking the bootloader erases userdata!
Lastly, you need to have fastboot and adb installed, go xda and google if you are not familiar enough with that.
Greets and good luck
Click to expand...
Click to collapse
I might try it... It looks a little difficult for me.
But what bothers me is the unskippable tutorial from the beginning that shows you how to use the 2 screens...
Anyways I can always use it for spare parts

TWRP not working anymore on Shield (2015) Version 7.2.1?

Hello everyone,
I've wasted my Christmas days to - unsuccessfully - re-root a Shield (16GB; 2015) after upgrading to Software 7.2.1. I need to use more than one USB mass storage device and to be able to copy from one to another, so I want to re-enable Stickmount.
The device was rooted before (which means the bootloader was already unlocked, too), and enabling USB debug, finding the device on my PC via "adb devices" was no problem, either. Issuing "adb reboot bootloader" went fine, too, the device could now be seen via "fastboot devices".
So, I flashed the TWRP image (I actually tried three different versions, 3.0.2, 3.1.1, and the most recent 3.2.3). All seemed to load fine (it spewed out two time values followed by OKAY, took about one second), but the reboot that follows only shows the NVIDIA logo forever without anything else happening (the longest I waited was 20 minutes) - according to the docs I could find (and had used before), TWRP should appear after about 15 seconds.
So, I'm stuck. I cannot get TWRP to start which prevents me from sideloading SuperSU, which means I can't use Stickmount.
Is there anything I did wrong? Is there any other way to get Stickmount installed onto my Shield? Any help is appreciated.
Cheers, Pit.

You'll need to wait until TWRP gets updated to get around the new android security measures. So keep checking TWRP website periodically to see when a new version is released.
You could have found this out if you went to Nvidia Shields Android TV forum and read some posts.

I was reading here, as well as at the nvidiashieldzone, where the tutorials are up, plus I was googling for the errors I was getting to no avail. Sorry for not finding every post on every forum on the internet, and thanks for giving the right pointer.
That means there is currently no way whatsoever to get the Shield rooted on 7.2.1., right?

Not just now, there's a guide to root 7.2 - using a developer image, and there's a chance of bricking - best to wait until TWRP is updated - also you don't need to root to use stickmount.
You only need to do something like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb shell
pm install -i "com.android.vending" -r /sdcard/Download/stickmount.apk
adb reboot
That way you can use your apk without being rooted - and your device will still be secure, and you can use widevine etc for netflix and other apps that check to see if your device is rooted.
Or you can just push the driver files stickmount uses like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb push hosts /system/etc/hosts (example file)
adb shell "chmod -R 644 /system/etc/hosts"
adb reboot

Thanks for the info - if I understand this correctly, I can install apks with root-like permissions using TWRP without rooting the whole device, right?
I will try that out once TWRP is working again.