Database Develop

Root the Nexus with ROM Links *Updated*

Root the Nexus with ROM Links *Updated*
-------Notes--------
1. This does void your warranty.
2. The root image auto installs the superusers permission app
3. I am in no way responsible for anything that goes wrong.
4. Once you unlock the bootloader it does a factory reset on your phone.
5. I don't mind people posting this tutorial on their sites for others to see and use but I do ask that I'm at least given credit for my work.
1. Download fastboot and adb files:
Here
2. Extract tools.zip to a folder and Open a command window in that folder by holding down your shift key and right clicking anywhere in the window and select open command prompt here
3. Then with your phone turned off hold the power and trackball to access the bootloader.
3b. Type this command to make sure your phone is connected and reconized. "fastboot.exe devices"
4. Once in the bootloader type this command in your command prompt "fastboot.exe oem unlock"
6. Follow what that sceen says.
7. Flash Amons RA Recovery Image from here
---------------Now to root your phone.---------------
1. Once you've flashed the recovery image turn your phone off.
2. Then power on by holding power button and trackball then tap the power button to access the bootloader.
3. From there use your volume keys to go down to recovery and hit power button again to access the recovery console.
4. Enjoy rooted phone
---------------Now to Flash a Radio and a Rom---------------
1-Download Radio(s):
Preferred:
RADIO UPDATE - 4.03.00.21_2 (from ERE27 update)
Original Radio image 4.02.02.14 (from ERD79) in an update.zip
2. Download a Rom:
A-[ROM] Enomther's TheOfficial Nexus1
B-[ROM] CyanogenMod
C-[ROM]MoDaCo Custom ROM with Desire/Sense
D-MoDaCo Enhanced ROM
2. put both the radio and update zips on your sdcard
3. power down your phone
4. Using the volume down key and power button to get to bootloader/recovery option screen
4a Use volume key to scroll and power button to pick
5. Go to flash zip from sdcard
6. Flash radio update zip first
7. After that is complete and you've restarted when it told you to do so.
7a. In recovery..direct to wipe menu and wipe phone.
8. Flash Rom zip
9. To get root again simply reflash the nexus-addon-0.1-signed.zip (instructions above.

Followings are instructions for OSX or any *nix platform.
Android SDK is nice to have but not needed.
You can download the Android SDK here.
I take no responsibility for what you do to your phone or your computer.
Step 1. Download the file from above post and unzip the file to your desktop.
Step 2. Open Terminal.
Step 3. Go to the folder that you zipped.
command:
cd ~ <enter>
cd Desktop/ <enter>
cd 1.1-nexusone-superboot/ <enter>
step 3. Load into fastboot on your phone.
<option 1> first power off, then power on while holding down the trackball.
or
<option 2>You can also hold down volume down while powering on and then select fastboot and press power.
step 4. Make sure fastboot can connect to your device.
command:
./fastboot-mac devices <enter>
if you can see the serial number of the phone with fastboot next to it, you are good. If not, repeat step 3.
step 5. Enter the following in your terminal screen
./fastboot-mac oem unlock (if you are on a mac)
./fastboot-linux oem unlock (if you are on a linux based machine)
step 6. If you do not want to void warranty or if you have not save your settings and contact etc, do not press yes. Save those first.
Follow instructions on screen. (use the volume up/down to switch and power to select).
Phone will reboot with unlock icon on the bottom of the X logo. Kiss your original setup goodby.
step 7. Enter the follow command:
./fastboot-mac flash boot nexusone.superboot.1.1.img <for mac>
./fastboot-linux flash boot nexusone.superboot.1.1.img <for linux>
step 8. Reboot phone by pressing volume down and pressing power. You are done!

i vote for a sticky!

i want to root so bad but i just cant bring myself to void the warranty on this 530$ device

melterx12 said:
i want to root so bad but i just cant bring myself to void the warranty on this 530$ device
Click to expand...
Click to collapse
577+change but who's counting right But I agree I don't know if I want to void the warranty just yet

aad4321 said:
CONFIRMED WORKING. Thank you. NOTE: THIS WILL RESET the DEVICE!!!
Click to expand...
Click to collapse
Can you LOCK the bootloader after unlocking it using the same steps? That would be a first step in restoring to normal if warrenty work is required.

What is this underclocked 2?

If nobody else gives it a try by the time mine arrives tomorrow, I will root my device and then see if I can't reverse it for the sake of warranty preservation.
Glad we are already at this step on Day 2

I did this and I can't see protected apps on the market anymore.. anyone else experience this issue?
A way to check is to try to find Twidroid on the market or really any paid app

djunio said:
What is this underclocked 2?
Click to expand...
Click to collapse
its not underclocked. its 1ghz.

im too scared to do it eventhough i knows its easy and no big deal

i think i'll wait until there is a reason to root the phone other then saying its rooted when there's a feature or ROM i can add that's useful like multi touch then ill root my phone.dont get me wrong i got this phone to root it but theres no point rite now

I'm getting mine in the mail tomorrow . I'm not going to root it right away though.. just in case something goes wrong ):

melterx12 said:
its not underclocked. its 1ghz.
Click to expand...
Click to collapse
did u root n check it?

aad4321 said:
I can see them still, and mine is rooted.
Also, I try to open the superuser permissions app and it freezes every time..This is also both with and without debugging enabled. Anyone else have this problem>?
Click to expand...
Click to collapse
Same issue here.

well maybe it is underclocked but I doubt it. Google advertises the phone at 1Ghz.

my permisson app doesnt freeze for me but what you can do is remove it and use something like astro to go to your phones root dir theres a folder in there called superroot with the apk for it so you can reinstall it.

Is there a unroot tutotial as well?

Paid Market Apps
I had a feeling, and it seems to have been confirmed, that rooting will not allow me to download paid apps. I know that this was an issue when the G1 was first rooted and it was "fixed." Can someone confirm this issue? This is a big one for me.

AndroidAppCritic said:
I had a feeling, and it seems to have been confirmed, that rooting will not allow me to download paid apps. I know that this was an issue when the G1 was first rooted and it was "fixed." Can someone confirm this issue? This is a big one for me.
Click to expand...
Click to collapse
I can still see paid apps.
Also, reinstalling the superuser apk fixed the blank screen issue.

G1 refuses to enter boot mode

I press and hold the [home] and [power] keys and it boots to nothing, even tried the [camera] and [power] keys on my G1, nothing. Current rom/SPL posted below, is it possible there's a changed key setting for the rom?
Rom: CaNNoN202-CompleteEclair-v2.0
SPL: Danger
Firmware version 2.1
Baseband Version 62.50S.20.17U_2.22.19.26I
Kernel 2.6.29.6-bfs-Firerat
Build Complete Eclair 2.0

Try reflashing the recovery image via terminal
$su
#flash_image recovery /sdcard/recovery.img "assuming your recovery image is n root of sdcard and you renamed the recovery image as recovery.img"
#reboot recovery
See if that boots to recovery

How can you get to the terminal if the phone won't boot past the first screen?
camera+power goes to the first screen, home + power goes to the first screen, trackball + power doesn't load a screen, but turns a blue led on.
I have adb. How can I do it using that??

techn0crat said:
How can you get to the terminal if the phone won't boot past the first screen?
camera+power goes to the first screen, home + power goes to the first screen, trackball + power doesn't load a screen, but turns a blue led on.
I have adb. How can I do it using that??
Click to expand...
Click to collapse
Does adb see your device?
At cmd prompt type
adb devices
If it shows up type
adb remount
If that works...
adb shell
You will have
#
Type the commands in the post above after putting a recovery image on your sd card.
If the first step does not work, you may be bricked.

techn0crat said:
How can you get to the terminal if the phone won't boot past the first screen?
camera+power goes to the first screen, home + power goes to the first screen, trackball + power doesn't load a screen, but turns a blue led on.
I have adb. How can I do it using that??
Click to expand...
Click to collapse
Just to clarify, the phone does boot up, and is fully functional aside from the [home] key working. I assume if I follow those directions, I could possibly use the android default img, and restore that, and unroot the phone for return possibilities?

rootlinuxusr said:
Just to clarify, the phone does boot up, and is fully functional aside from the [home] key working. I assume if I follow those directions, I could possibly use the android default img, and restore that, and unroot the phone for return possibilities?
Click to expand...
Click to collapse
From cmd prompt type
adb reboot recovery
See what it does.

I tried to type that and now my E, and R keys are dead...I even tried purchasing Better Terminal Emulator on the news that I can use the virtual keyboard and/or copy paste text. While this works, it allows SU, but when I type
PHP:
adb reboot recovery
it says "sh: adb: not found" So what I figured I'm stuck doing is to restore it to non-root status, or is there a way I can run commands on it from my laptop? The phone itself works great, makes calls, sends txt messages, just won't let me press the [home] key, and now apparently the E, and R keys.
EDIT:
I installed JDK, and the ADB packages, and can get it to the recovery screen from that menu, but I've run into another issue in regards to installing any update.zip through the cyanogen recovery menu. That being that you have to press [home] to confirm you want to do any action...

rootlinuxusr said:
I tried to type that and now my E, and R keys are dead...I even tried purchasing Better Terminal Emulator on the news that I can use the virtual keyboard and/or copy paste text. While this works, it allows SU, but when I type
PHP:
adb reboot recovery
it says "sh: adb: not found" So what I figured I'm stuck doing is to restore it to non-root status, or is there a way I can run commands on it from my laptop? The phone itself works great, makes calls, sends txt messages, just won't let me press the [home] key, and now apparently the E, and R keys.
EDIT:
I installed JDK, and the ADB packages, and can get it to the recovery screen from that menu, but I've run into another issue in regards to installing any update.zip through the cyanogen recovery menu. That being that you have to press [home] to confirm you want to do any action...
Click to expand...
Click to collapse
adb is ran from your computer, not terminal.
and yes, your home key not working means you won't be flashing a new rom through recovery anytime soon.

Once I figure out how to push an update package(rc33) and upgrade to cupcake/donut, will it be effectively unrooted(for purposes of sending it back)?

rootlinuxusr said:
Once I figure out how to push an update package(rc33) and upgrade to cupcake/donut, will it be effectively unrooted(for purposes of sending it back)?
Click to expand...
Click to collapse
you don't push it. and you don't technically "upgrade" to cupcake. you downgrade.
however, yes, it will be ok to send back.
here's how:
http://forum.xda-developers.com/showthread.php?t=491350

Reboot

Is there a way to reboot this thing without root. All the apps seen need root. Why isn't it available with the power button anyway? Am I missing something?

PolishPoet said:
Is there a way to reboot this thing without root. All the apps seen need root. Why isn't it available with the power button anyway? Am I missing something?
Click to expand...
Click to collapse
Root access is needed but the only way I know how to do it without root is with a computer via usb connection; install minimal adb and fastboot by shimp 208 and run through command prompt. Make sure you have updated motorola drivers and connect your phone, run command prompt and change directory to wherever you have adb installed; type "adb reboot" (without quotes, you may include -bootloader or -recovery to go into either of those); to install, go here.
http://forum.xda-developers.com/showthread.php?t=2317790

I've just moved to this phone from my S3, and it seems I have been spoiled by CM through the years, as the first thing I noticed about the OS was all the features I frequently used -- including a "reboot" menu item, which I wouldn't have considered a "feature" until now. The best part: when I first turned the thing on, it tried over and over to activate itself but failed, with the error message telling me it would try again the next time I reboot the phone. And how would you suggest I perform that reboot? This one I'm sure is trivial to most by now who have been using this phone for a while, but it just blows my mind.
Is shrimp's adb fastboot accepted as a recommended and reasonable workaround for this?
BTW, what other "features" am I going to notice are missing soon (and any recommended apps/methods to replace them)?
Thanks.

Doesn't just holding the power button a few seconds "reboot" the phone...or is that not really a reboot?

wjdunn3 said:
Doesn't just holding the power button a few seconds "reboot" the phone...or is that not really a reboot?
Click to expand...
Click to collapse
More of a hard power-off and back on than a clean reboot, and you would lose state and cached data, which to me isn't worth the risk.

need help, installing ota zip to my nexus 6

Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
I was having the exact same problem last night, following the same instructions. I still could not figure out how to sideload the OTA, so I ended up just flashing the update and starting from fresh. Wish I had the answer for you.
Here was my thread asking pretty much the same thing: http://forum.xda-developers.com/nexus-6/help/disconnects-computer-entering-bootloader-t3230705

danarama said:
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
Click to expand...
Click to collapse
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
In the command window — make sure you are in the directory where ADB and Fastboot reside — type: “adb sideload [the full name of the file].zip” without the brackets around the file name.
The update will install and reach 100 percent.
Reboot and enjoy the latest version of Android Marshmallow.
Click to expand...
Click to collapse
(red arrow) and then the cmd says the null error, i am trying this now
I had the same problem. Turned MTP on and then it worked. You're told to turn it off but don't... Its in Settings-Storage-touch the ... Menu top right corner, USB settings and turn ON MTP mode. It worked well for me. I also used the Nexus Root Toolkit - makes things much easier!
Click to expand...
Click to collapse
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)

hendyanto said:
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
(red arrow) and then the cmd says the null error, i am trying this now
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
Click to expand...
Click to collapse
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.

danarama said:
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
Click to expand...
Click to collapse
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.

hendyanto said:
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
Click to expand...
Click to collapse
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)

I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!

danarama said:
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
Click to expand...
Click to collapse
qwerty1gr said:
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
Click to expand...
Click to collapse
Thank you guys! But after this "happy"night, i woke up to the OTA for marshmallow arrived on my phone, so see you guys on the rooting section instead, Thank you thank you for the help

[Guide] [One UI 3] How to boot into recovery in One ui 3 & above without a pc and root access

Reboot Your Device Into Recovery Mode
There are multiple ways to reboot an Android device into recovery mode. But after the latest OneUI 3.0 update, Samsung does not allow booting into recovery without connecting your phone to a PC with a USB-C cable. Here's a solution to easily reboot to recovery.
The steps mentioned can be applied to boot into both the stock recovery as well as a custom recovery if you have one installed.
Reboot to recovery without root access and without connecting your phone to Laptop/Pc.​
Download & Install LADB - Local ADB shell from playstore or download it directly from here.
Open Settings > About Phone and tap on the “Build number” field 7 times. This will enable “Developer Options.”
Go to Settings > System > Developer Options and enable “USB debugging” and “Wireless debugging.”
Open the LADB app. It will show a “Pairing information” dialog.
Open the recent apps screen. Press and hold on the app’s icon and tap “Split Screen” to open LADB in split-screen multitasking view.
On the bottom half, open Settings. Go to System > Developer Options > Wireless debugging. Tap on “Pair device with pairing code.” You’ll see a “Pair with device” dialog pop-up.
Copy the 6 digit “Wi-Fi pairing code” and paste it into the “pairing code” box in LADB. Copy the 5 digit port number from the IP address (the 5 numbers after the colon) and paste it into the “Port” box in LADB.
Hit “OKAY” in LADB and you should hopefully see text that says "Hello World”
Enter "reboot recovery"
And done now your phone will automatically reboot to recovery.
Note :
You can even try out different adb commands like deblooting system apps, allow permissions to apps like macdriod, system ui turner, etc and many more other adb commons without root and without a PC. (tested on Galaxy M30s)
Thanks to the developer of LADB
For downloads and other instructions : Click here

Reserved..

thanks .. good tut and very useful

Power off, then hold volume up and bixby button till recovery comes up. Works without a pc or cable.
realbbb
Moldly Going

realbbb said:
Power off, then hold volume up and bixby button till recovery comes up. Works without a pc or cable.
realbbb
Moldly Going
Click to expand...
Click to collapse
It's for users without root and pc

razs.originals said:
It's for users without root and pc
Click to expand...
Click to collapse
Power off, then hold volume up and bixby button till recovery comes up works for root, no-root, pc, or no-pc. It does not matter what version of OneUI.
realbbb
Purely Board

realbbb said:
Power off, then hold volume up and bixby button till recovery comes up works for root, no-root, pc, or no-pc. It does not matter what version of OneUI.
realbbb
Purely Board
Click to expand...
Click to collapse
Okay it might be working that way for you but many users reported that without connecting USB they aren't able to boot into recovery
recovery mode in android 11 one ui 3.1
Guys anybody know that how to go recovery mode in android 11 ( one ui 3.1 )
r2.community.samsung.com

Will this let me unlock bootloader?