Database Users

Unfinished rooting nexus one , please help

hi
I have a Nexus One on Official 2.3.4 update and i'm trying to root the phone, i'm having a hard time with the recovery image, I really like to know what i should do next.
1. read lots tutorials
2. Installed Android SDK and USB Driver for ADB thingy
3. downloaded and put fastboot in platform-tool and successfully unlocked bootloader
4. cannot get recovery to work, intended to install clockworkmod and RA one both give me the ! logo when i intend to boot in it
Questions
1. Should i downgrade first and then do this, if so, how does it work (if someone have a link to step by step tutorial)
2. Other methods
thanks a million

How are you trying to install recovery, and what errors/results are you seeing? Should be:
fastboot flash recovery name-of-recovery.img
How are you booting into recovery (if you reboot the phone, you will lose recovery)? Should be:
fastboot boot name-of-recovery.img
No need to downgrade. An unlocked bootloader is all you'll ever need...

danger-rat said:
How are you trying to install recovery, and what errors/results are you seeing? Should be:
fastboot flash recovery name-of-recovery.img
How are you booting into recovery (if you reboot the phone, you will lose recovery)? Should be:
fastboot boot name-of-recovery.img
No need to downgrade. An unlocked bootloader is all you'll ever need...
Click to expand...
Click to collapse
i install recovery that way yes, but i didn't boot that way, thanks i will try right now, will report back
EDIT - that works thanks so much, now i'm gonna attempt to root.

now i encounter another issue
so far i been following this guild http://forum.xda-developers.com/showthread.php?t=636795
and i cannot reboot to recovery after vol down+power menu.
do i just enter recovery with fastboot boot command and go from there?
what would be a better guild from this point on?

Place these two files on your sd card:
su zip: http://db.tt/BJudP0L
fix recovery zip: http://db.tt/ooDaCnU
Boot into recovery from the fastboot command, choose the flash zip from sd option, and flash the two files (one at a time). Done!

awesome, i had them installed. what's su and why is it recovery fix, if u don't mind can u explain these 2 files a little bit?
and what's next, do i just put the rom i'm flashing in the SD Card root and use recovery mode to install the zip?
going to use Cyanogen 7 for nexus one (update-cm-7.0.3-N1-signed.zip)
and also, what is this Google Add-on i read from the tutorial?

tripleccreation said:
awesome, i had them installed. what's su and why is it recovery fix, if u don't mind can u explain these 2 files a little bit?
and what's next, do i just put the rom i'm flashing in the SD Card root and use recovery mode to install the zip?
going to use Cyanogen 7 for nexus one (update-cm-7.0.3-N1-signed.zip)
and also, what is this Google Add-on i read from the tutorial?
Click to expand...
Click to collapse
su is short for superuser.. its basically using the root user account..
btw 7.1 RC is out if youre interested.. also take a look at the nightly releases

If you're going to install a custom rom like cm7 you do not have bother with the su part.
Put cm rom on the sd ( can be anywhere you just navigate to it) and the google addons (those or the gapps like the market etc.)
Flash custom recovery
Boot directly into the recovery (if you boot the os it overwrites the new recovery with the stock one)
Flash cm7
flash gapps.
reboot into cm7...
Your custom recovery will now stay there until you either flash a different one. Or flash a stock rom.

grimey01 said:
su is short for superuser.. its basically using the root user account..
btw 7.1 RC is out if youre interested.. also take a look at the nightly releases
Click to expand...
Click to collapse
should i just install the rom zip file in recovery mode? I'm not 100% sure what i'm suppose to do

albundy2010 said:
If you're going to install a custom rom like cm7 you do not have bother with the su part.
Put cm rom on the sd ( can be anywhere you just navigate to it) and the google addons (those or the gapps like the market etc.)
Flash custom recovery
Boot directly into the recovery (if you boot the os it overwrites the new recovery with the stock one)
Flash cm7
flash gapps.
reboot into cm7...
Your custom recovery will now stay there until you either flash a different one. Or flash a stock rom.
Click to expand...
Click to collapse
great, now u said flash cm7 do u mean "install zip file" but pick the cm7 file?
also, google add on, where should i acquire it?

also, for nightly release of cm (cm7.1 rc) for nexus one i should download the one called "passion" is that correcT?
http://download.cyanogenmod.com/?type=nightly

Also forgot to mention to do a wipe before you flash. That is also done in recovery.
gapps http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip That is
In recovery you pick install zip file. You then browse to your cm7 rom.zip or any rom for the matter and install. Do the same for the gapps. Do the same for any other flashable zip like kernals etc.

Yes. Nightly/stable/RC's all have to passion (nexus 1)

Also for future reference post ?s in the Q and A section. A mod will probably move it there or delete this thread.

albundy2010 said:
Also for future reference post ?s in the Q and A section. A mod will probably move it there or delete this thread.
Click to expand...
Click to collapse
Great!
i will keep that in mind for sure.

Update: Method Works now i know how to flash and root nexus one, awesome guys thanks a million.
Conclusion and Steps I did (probably helpful to many people like me research tons different tutorials)
1. Download Android SDK and install it,
2. Find "Nexus One USB Driver" download and install it, now install bootloader (follow guide here, but only do up to the boot loader part http://forum.xda-developers.com/showthread.php?t=636795)
3. Find "fastboot" download and extract it to Android SDK installation folder (one called Platform-tools)
4. download a recovery img, i got clockwork 3.0.0.5.
5. download the su (super user) (i dunno if this is necessary but i did it anyway, links are in previous replies) and copy the zip file to ur sd card.
6. download the custom rom u want to use and copy to sd card as well (i use cyanogenmod 7.1 rc here)
7. download the google addon and copy the zip to the sd card as well (link provided in previous replies)
8. go to start and type cmd to load up command prompt in windows (i use windows 7)
9. get to c:\program files (x86)\android\android-sdk\platform-tools\ (i use windows 7 64bit, if it's 32bit system, no need for (x86))
10. hold trackball + power to enter bootloader and fastboot usb enable (should be automatic)
11. type fastboot flash recovery [recovery name.img] (in Windows Command Prompt)
12. type fastboot boot [recovery name.img] (in windows command prompt)
13. do a backup first, then wipe all data and cache, and then navigate to "install zip" and install su, recovery fix, custom rom, google addon, one by one b4 restart
14. after all done, restart, and that's it.
it works for me. but of course, i'm pretty noob, you are still taking ur own risk if u follow my experience..

Step 5 (recovery fix) is only necessary if you are sticking with a stock ROM. All it does is delete the two files that restore the stock recovery. These two files are only in the stock ROM, which is why you don't need to do this if you install a custom ROM...
Also, as started earlier, you can also skip the su zip if you plan on installing a custom ROM...

Custom Recovery & Xposed for 5.1

NOTE: Do at your own risk and always make a backup before.
How to install custom recovery, root and Xposed for 5.1
Requirements:
1. Unlocked Bootloader
How to unlock Bootloader http://www.phonearena.com/news/How-to-unlock-the-bootloader-on-Motorola-phones-Moto-X-Moto-G_id53876
2. ADB drivers
http://forum.xda-developers.com/showthread.php?t=2588979
3.TWRP
https://dl.twrp.me/ghost/twrp-2.8.7.0-ghost.img.html
4.Xposed
Zip File: http://forum.xda-developers.com/attachment.php?attachmentid=3543415&d=1447616638
apk: http://forum.xda-developers.com/attachment.php?attachmentid=3392105&d=1436123813
Steps:
1. Copy the twrp file to the folder where adb drivers are installed (generally C://adb) and rename it to twrp.img. Copy both the zip and apk file of the xposed to your phone memory.
2. Enable usb debugging in your phone and connect it to your pc.
3. Open cmd in the adb folder by pressing LeftShift and right mouse button and select open Command prompt here.
4. Type adb reboot bootloader. Or shut down your device. Press vol down+power for abut 5secs and release it.
5. Type fastboot flash recovery twrp..img
6. Go to recovery on your device by pressing vol down and select it by pressing vol up.
7. Go to reboot and select system. Swipe to install SuperSu
8. After your device boots up update the SuperSu app.
9. Boot your device to twrp recovery.
10. Select install and select the xposed zip.
11. Reboot your device.
12. Install the xopsed apk.
13. Reboot.
DONE :good:
List of xposed available for 5.1: http://android.wonderhowto.com/inspiration/complete-list-lollipop-compatible-xposed-modules-0160380/
Original thread for xposed: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Original thread of SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053

FIX for Mobile Standby Battery Drain
Download this apk
Activate the module in Xposed.
Reboot.
Original Thread: http://forum.xda-developers.com/xposed/modules/xposed-mobileradioactivefix-t3132956

You have old versions of the APK and Installer, here are the latest versions that I have confirmed working...

mastarifla said:
You have old versions of the APK and Installer, here are the latest versions that I have confirmed working...
Click to expand...
Click to collapse
i will update them in the op. i haven't tried it so i didn't post it

good thing you made this
fastboot or mfastboot?? i do it using mfastboot... because since the beginning i've been seeing people using mfastboot.... i guess it has to do something with the write persmissions HERE

jcrahul said:
fastboot or mfastboot?? i do it using mfastboot... because since the beginning i've been seeing people using mfastboot.... i guess it has to do something with the write persmissions HERE
Click to expand...
Click to collapse
you can use fastboot also. mfastboot use is mainly for multiple fastboot files or large file. it is used to flash system.img because it has multiple files and its size is too large for fastboot

Thanks! Worked like a charm! And, one more question.. Can I do a Wipe Cache Partition? Will it cause my phone's to be unstable? And, after installing several mods (modules, I'm witnessing a battery issue.) So, my question is, Performing a Wipe Cache Partition will have any affect on my phone? And Will it improve my battery performance? Thanks in advance!

Vampirexox said:
Thanks! Worked like a charm! And, one more question.. Can I do a Wipe Cache Partition? Will it cause my phone's to be unstable? And, after installing several mods (modules, I'm witnessing a battery issue.) So, my question is, Performing a Wipe Cache Partition will have any affect on my phone? And Will it improve my battery performance? Thanks in advance!
Click to expand...
Click to collapse
You can wipe partition cache. it will not make your device unstable but clearing cache many times is not good.

OP updated with latest Xposed zip, apk and TWRP 2.8.7.0

How to uninstall it?

How to root CM12.1 and SLIMLP 5.1.1 roms?

I usually install superuser.zip with TWRP recovery. This time I tried both latest twrp with f2fs support on SD card and TWRP on nand, but looks like all zip files I install with recovery trying to apply to nand and nothing happens. I installed Superuser apk, but that way it tells i need install superuser via recovery and all apps tells me I have no root, but I have root access with adb shell. Fresh install CM12.1 hd2 rom with two ext4 partitions. Note: I tried mounting two sd-ext partitions before installing superuser in recovery. Also I tried to replace su binary under /system/xbin/su in rom archive itself. After installation su file is correct and permissions is right, but Superuser still ask me to install self through recovery, and apps can't get root. I even tried install SuperSu, but still without success.

Looks like its really easier then I thought. I just need enable developer options and activate root under Developer section.
Video: youtube.com/watch?v=Knm1kKVkJd8
Thanks: macs18max

Flashing Open GApps with AROMA installer reboot.

So I always use Open GApps with AROMA installer as my GApps of choice since I can pick what I want to have installed. I'm using TWRP 3 but everytime I want to flash Open GApps with AROMA installer it will reboot back into the recovery. I have to tried installing a few times before it will install correctly. Does anyone know of a fix to this? :/ Other Open GApps works fine but I prefer the one with AROMA installer.

Tried it for the first time today (always used other packages before) but to me it's broken...It does the same as you on another device (S5)...I guess somewhere there must be a solution to this.

It is at this time not solved.
Have someone a idee?

CyberHawk44 said:
It is at this time not solved.
Have someone a idee?
Click to expand...
Click to collapse
Reroot your phone with kingoroot then transferall the zip files to to extSD card make sure u have extracted the twrp image file. Then download an app called Flashify from the play store . Open the app go to recovery choose file from the sd card i.e recovery.img and flash it . After this reboot ur phone in recovery mode follow the procedure of flashing files to install CM13 and Gapps

@Frappy @CyberHawk44 @LinoX this is a workaround that worked for me:
wipe cache/data etc..
flash your desired rom + Su/Xposed/etc..
wipe cache/dalvic cache
reboot into TWRP
then flash Aroma gapps
Give it a try it works

I know that all and have many try but I think I have found it. I must try it more...

Follow gapps on git hub having issue id : 503
TLDR; Just mount system folder also in twrp and then install gapps.

Trouble Permanently Flashing TWRP

Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance

Rawrden said:
Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance
Click to expand...
Click to collapse
The basic "mechanics" of what happens seems to still be as follows:
As your phone is delivered with Stock OS, it has these two files installed:
Code:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I know from looking at mine when I got it that it had /system/recovery-from-boot.p installed. If it's there, it is run when it runs at boot.
To stop that behavior you have to get rid of those files before you reboot the first time from recovery or else recovery will be replaced with the stock image. I'm aware that supposedly the custom recovery supposedly renames either one or the other or both of these but am not convinced it does this or whether installing root (either Magisk or SuperSU) does it. Either way, since you're stuck with the problem, either from file-manager in TWRP if that's all you can boot to, you need to rename /system/recovery-from-boot.p to something like /system/recovery-from-boot.p.orig and maybe the other one /system/etc/install-recovery.sh to /system/etc/install-recovery.sh.orig as well.
Once even the .p file is gone, it's not going to rewrite recovery. You must, of course, be rooted before you can touch those files although if you can sideboot TWRP, it seems like you are rooted while it is booted and "should" have access to system files if you can mount system rw.
I've fixed it this way on other phones. On this one, installing the "official" TWRP and Magisk did it. When I booted into /system after installing Magisk, I looked for the .p file and found it renamed to /system/recovery-from-boot.bak.
I found a link for a Samsung s8 for the same purpose. It's probably identical. http://www.teamandroid.com/2017/04/25/install-galaxy-s8-twrp-310-recovery/3/
Click to expand...
Click to collapse

I looked into those two files while in TWRP and noticed I only had the recovery-from-boot.p file. This was already in fact renamed to recovery-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?

Rawrden said:
I looked into those two files while in TWRP and noticed and only had the recovery-from-boot.p file. This was already in fact renamed to record-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
Click to expand...
Click to collapse
To me, it doesn't sound like a conflict to re-install Magisk over itself in FOS and see if that helps. The real "action" that counts is all about whether you've already booted into the OS after installing TWRP and then how you go about getting rid of the .p file without doing a regular reboot via the OS. Even installing the FOS ROM should get rid of the .p file (rename it), so something else is going on. I'll look around some more and update this if I can.
By the way: Depending upon how exactly you got from TWRP to the OS the first time, it could already have rewritten the stock recovery by the time you noticed *.p file renamed to *.bak.
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
---------- Post added at 09:26 AM ---------- Previous post was at 08:59 AM ----------
Rawrden said:
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?
Click to expand...
Click to collapse
Just saw this note:
Anytime you're in TWRP, you're automatically "rooted" for the time you're there. It's integral to TWRP having permissions to do anything like install etc. If you just "loaded" TWRP (as in fastboot boot twrprecovery.img) then you'd be rooted, but when you rebooted to the system, you'd be unrooted. While you were in TWRP, in theory you could make file system changes to the /system partition (a) if TWRP lets you mount it rw which I think that first swipe does and b) if you can see the correct files in it's file manager.
So it "seems" like those file changes should be actual file changes to the correct place. Keep in mind that while booted in TWRP, TWRP may have it's own ./system/ that has nothing to do with the OS's ./system folder, so you've got to be able to mount the OS's ./system. TWRP's ./system is already fine and of no importance for this. I can boot mine into TWRP and look around to try to clear this up, but it might not be crystal clear to me either.
The output of a TWRP terminal emulator "mount" command might be of use but it will be messy. Maybe if you can do this in emulator from TWRP:
# mount | grep system, and look at that output, perhaps put it in this post, it'd be of help. The mounted rw ./system we need is going to be the same one you'd see from adb shell or terminal emulator while booted from the OS. My guess is that the one we don't want from TWRP's perspective will be mounted as /system (params...) and that the the OS's system either will not yet be mounted and you'll have to go to mounts and mount it and then look at the output of the mount cmd again to figure out what it was mounted as. Sorry about how complicated this explanation has become. Anyway: The ./system that corresponds to the OS is the only one we care about.
There's no easy way to explain it so I'll leave it hidden to spare anyone having to look at it:
I just booted into TWRP and used terminal emulator and file manager to explore:
findings: While in TWRP, using terminal emulator to do a
$ df and then a $ mount command shows no ./system mounted specifically. // maybe not a surprise.
// TWRP just mounts it's root / file system and there is a /system folder, just not a specific mount point for it.
// TWRP does not auto mount the OS's ./system partition by default. It depends what you're going to do there.
Without going into "mounts" and clicking on /system, it won't even try to mount /system for the OS.
If you can get that mount to work in read/write mode, then you should be able to see the ./system mount using terminal emulator as such.
$ mount | grep -i system (and look specifically for ./system on the right side of whatever appears).
In theory you should be able to make changes to the OS's /system partition now. When you're done, unmount it. (I'm assuming all this works from TWRP, a dodgy assumption)
At this point: I'm just trying to figure out how TWRP does things like installs OS zips to the /system & /data partitions which it is clearly successfully able to do. It could do it without mounting anything because it could use the linux dd command, which just writes to the /dev name. OR: It could mount /system and use it. I'm not sure which.

hachamacha said:
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
Quote:
Code:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?

Rawrden said:
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?
Click to expand...
Click to collapse
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.

hachamacha said:
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.
Click to expand...
Click to collapse
Done! Can I just say how grateful I am to you for helping me out with this? Your answers have been extremely detailed and I've learned quite a few things. Unfortunately I can only thank your posts once, because you've earned more than that. Thanks again and keep being awesome!