Database Develop

[Q] cant boot into recovery

so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04

drawde40599 said:
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
Click to expand...
Click to collapse
Use fastboot to re-flash recovery img

lcchan1 said:
Use fastboot to re-flash recovery img
Click to expand...
Click to collapse
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?

drawde40599 said:
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
Click to expand...
Click to collapse
download clockwork recovery from the app store.
Flash its recovery, then boot into recovery after a successful flash.
Out of curiosity, why did you install a non-rooted version of 2.3.3.?

You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.

Rusty! said:
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Click to expand...
Click to collapse
HELL YA !! thank u much

Thread moved to Q&A, a sub-forum dedicated exclusively for questions like these. Please post all further questions here. Do not post new question threads in development, as you are not doing any even remotely related to Android development. That said, I'm glad you were able to figure out your issue.

Downloading clockworkmod will not work. He is not rooted so he can't flash the recovery with it.
Sent from my Nexus One using XDA App

This happened to me 2 days ago (word by word)!!
From Amon Recovery's page, this is what the problem is:
"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). More info on this here"
Here: http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
My problem was even more complicated because I tried flashing froyo without a wipe so my phone started going into boot loop!
Thanks to danger-rat's reply, I was able to get into recovery at least once and then everything came back under control. He 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..."
Here's my thread:
http://forum.xda-developers.com/showthread.php?t=980577
edit: I just realized that you are not able to fastboot either? I was able fastboot and flash recovery onto my phone and then without turning the phone off - I was able to go into recovery straight after flashing amon_recovery.img

passimg back to an earlier version of Android, root, then install a pre-rooted GB...
If you get the "main version is older" error, you're out of luck and your only option is to unlock the bootloader or wait for a new method to be found...
Sent from my Nexus One using XDA App

Stuck in Hboot. Can't access recovery. Help?

GSM SLCD Nexus One
Hboot 0.35.0017
S-On
Locked Bootloader
Somehow I managed to get stuck here, I'm still not sure how. If I had to guess it would be the bootmanager application, although I haven't used it since this morning.
I really would like to keep the bootloader locked if at all possible. The phone was rooted before.
I figured I could just flash a recovery that's signed (hboot signature verification fails on cwm and amon_ra, via fastboot) but I can't for the life of me find one.
In the bootloader, I click on recovery, shows the n1 splashscreen briefly, then sends me to fastboot.
Thanks for the help.

You won't be able to put a custom recovery on there without unlocking the bootloader or reseting your phone. If you are really wanting to keep the bootloader intact, the easiest thing would be to do the PASSIMG method. Have a look in the wiki and it will explain everything to you. Then once you get back into Android, root the phone before it updates to Gingerbread and then install ROM Manager to get your custom recovery back.

I actually just ended up unlocking it and using fastboot to put a new recovery on it. I didn't know about the PASSIMG method. Thanks for your response anyway though.

[Q] lost root after 2.3.6 update

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...

[Q] Bootloader questions

From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?

cytherian said:
From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?
Click to expand...
Click to collapse
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.

Shelnutt2 said:
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.
Click to expand...
Click to collapse
Thanks for the info, Shelnutt.
I'm kind of in a peculiar "Nexus" that I'm trying to extricate myself from. I have S-ON presently. I would like to change it to S-OFF, but I can't seem to do it. I suspect it's the bootloader preventing me, which is hboot 1.7. So, I tried to replace the bootloader and the attempts fail. I've tried it through the adb shell, fastboot, terminal emulator on the phone, and via the recovery manager (TWRP). Attempting to replace the bootloader results in "signature verify fail". Through TWRP, it also said verification failed.
I also tried to retrieve the identifier token (HTC dev) so that I could unlock the phone that way, but "fastboot oem get_identifier_token" fails with a "Command error" (although I can execute "fastboot oem rebootRUU" with no problem).
I also tried to use Regaw's boot mod tool, which replaces the bootloader and turns S-OFF. But it aborts because my Hero is already rooted. So I went into my z4Root application and selected "un-root". It said "done", but the phone remains rooted. I even tried to "Re-root" but it wouldn't complete (thinking if I root it again, I could then try another un-root).
I'm thinking I should just flash back to stock, but... I don't have any fresh nandroid backups to use. TWRP doesn't do nandroid. It does its own thing, which becomes a problem because TWRP needs Android 2.2 or higher. So... does that mean I need to install ROM Manager again, do a nandroid backup, then run an RUU back to full stock again?

For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k

Shelnutt2 said:
For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k
Click to expand...
Click to collapse
Thanks, you're right... in TWRP there's a checkbox to control that. There's also one to verify md5, but it requires a file (I guess it looks for [filename].md5). In any case, getting past that resulted in failure to load hboot 1.46 as you surmised.
The issue with Regaw doesn't seem to be the radio. It simply reports that there's nothing to do because the phone is already rooted. Apparently it will only run if the phone is not rooted. And to unroot, it appears the only way is by RUU. Z4Root is supposed to allow it, but when selected it doesn't do anything.
So, I finally came up with something that got me on the right path. :good:
I re-installed ROM Manager and flashed the latest ClockworkMod to Recovery. From there I could apply the hboot 1.46 ENG-SPL with no issues. I rebooted into the bootloader and saw................ HERO XC ENG S-OFF, HBOOT-1.46.2000. :highfive:

[Q] need some serious help with return to stock

hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19

Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..

Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.

Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA

still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.

1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.