Related
a while back i encountered some sort of error that caused my boot1 partition to disappear, leaving a gear-type-image on bootup
i believe i was doing something with adb. I know there is a command in adb to delete a partition, however i could not find one to recreate a partition, so i have been stuck with this gear since then
it's not a major issue, as it has no real effect on performance, and it doesnt show up unless i boot my phone, which i never turn off, however if there is a way to fix it, i would like to.
anyone got any ideas on how i could restore my boot1 partition?
is it the first image that appears on your phone or after that where the animation should be?
it's the first image.
it appears where the "Rogers" logo would be
if you can find the original rogers boot image, it may be in the rogers real root thread by haykuro, you can fastboot flash splash1 nameofsplashimage.rgb565 and that should fix it. the first image when your phone boots up is called splash1.
that is exactly the issue, when i try to flash my splash1, it tells me the partition does not exist
just wanted to bump this one, kuz im still lookin for the answer
1)find a splash image on these forums (it should be in .rgb565)
2)then boot into bootloader mode, and press back until youre in fastboot mode
3)connect the phone to USB, the screen should not show fastboot USB
4)On PC open console and type in adb fastboot flash splash1 [Directory to your splash image file eg C:/Android/Mysplash.rgb565]
5)Reboot the phone
or if you just want to flash the stock splash image follow these instructions
http://forum.xda-developers.com/showthread.php?t=473248
you need to have a non perfect SPL for this to work but since you managed to delete it im assuming you already have one lol
Hello guys,
I know the first thing you may think is this is another moron who bricked his Cell. But please be patient with me and at least let me learn from my loss. Please let me know what I did wrong.
First I read 3 main thing before doing anything,(1) [Guide] One-Click Root for Rogers HTC Dream:, (2) the post by HYKO and and finally CyanogenMod Wiki. Since I cannot post URL I attached them at the end.
So first I tried to get a hboot 1.33.2005 SPL using the source (1) which went ok.
then I used CyanogenMod Wiki (3) to root my HTC DREAM. Every thing went ok till I tried to update the radio. After I flashed the radio my cell hangs on the rogers logo and does not go any further. I can go to the fastboot (camera butt and END). it is S-off and 1.33.2005 SPL. However, I can not reach the recovery menu (Home and END). I tried flashing back to the older radio 3.22.20.17 and 2.22.29.26I (using the haykuro zip file). none of them worked.
First I want ot know what did I do wrong. Second I noticed my SDcard is broken, and the HBOOT looks for deaimg and deardiag on sd. does anyone know if I can unbrick it using this.
Thanks
alrsar
(1)
1. Download Haykuro's root kit here.
2. Extract the recovery.img and update.zip files from the download and copy them to the root of your sdcard's fat32 partition (if you haven't partitioned your card yet for A2SD, then just the root of the card itself).
2. Last time I checked, the one-click root app, flashrec, has been pulled from the Market, so download it here.
3. Install the app and start it, it will look like this:
4. Tap 'Backup Recovery Image', in some cases the app will fail to backup the image. This shouldn't be a problem, but if it works, it's always nice to have a backup.
5. In the blank above the greyed-out button enter '/sdcard/recovery.img' without the quotes. If you were successful in making the backup, the top button should change to white and say 'Flash Custom Recovery Image'. If not, don't worry, there is a hidden button to the right of the backup button that will bypass the backup requirement. Like so:
6. Press 'Flash Custom Recovery Image'. If you get a flash failed message, try flashing with your phone unplugged from USB.
7. Power your phone down.
8. Power up your phone while holding the home button. You should get the older 1.2 Recovery Menu. If your phone hangs at the Rogers logo, remove your battery, re-install or try the 3-finger salute (Phone, menu, and power button together) and try again. If it still hangs on the Rogers logo, reboot without the home key, this will bring you back to normal boot. You won't be rooted but you won't be bricked.
9. Once you're at the recovery menu, choose the second option, apply sdcard:update.zip. In some cases you may get an error something like E: not found. If you choose the second option again, it should find the update.zip alright and then press home to continue.
10. Now click on reboot (Home & Back). Press and hold the camera button and you should boot into the new 1.33.2005 SPL.
11. If all has gone well and you see hboot 1.33.2005, you can safely follow the rest of the rooting instructions in this thread. There's also a great set of instructions for installing Cyanogen's 4.2.X roms in the same thread. The post is here.
Of course, these instructions may be rendered moot if Rogers chooses to fix the vulnerability that allows one-click root at which point we'll have to hope someone manages to find a way around the so-called 'perfect' SPLs.
If after a couple attempts you remain stuck at the Rogers logo, remove the battery, reinstall it and then power up normally. You should then boot back to the unrooted phone and it will restore the default recovery. You may not be rooted, but at least you're not bricked.
(3)
1. You will need fastboot on your computer to run the following commands. Set up ADB and fastboot on your computer.
2. Download exploid & Amon_Ra's Recovery:
* exploid (includes the source): Download
* Amon_Ra 1.7.0: Download
3. Rename Amon_Ra's Recovery Image to simply recovery.img.
4. Put both the exploid file & Amon_Ra's Recovery in the same directory as adb.
5. Turn on USB Debugging (Settings » Applications » Development).
6. Connect the Rogers Dream to the computer.
7. On the computer, open terminal & navigate to the adb folder
cd /path/to/adb/
8. Type in the following commands:
adb push recovery.img /data/local
adb push exploid /sqlite_stmt_journals
adb shell
cd /sqlite_stmt_journals
chmod 777 exploid
./exploid
9. You will see a message come up. The exploit has now been setup. Unplug & re-plug in the USB cable to the computer.
10. Now type in the following commands:
adb shell
rootshell
NOTE: This will prompt for a password, the password is "secretlol".
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
NOTE: The first time this command runs, it may return "mtd: read error at 0x00000000 (Out of memory)". Simply run this command again & it should run without error.
11. The Rogers Dream has now been rooted & will have Amon_Ra's Recovery on it.
Flashing Radio
If the Rogers Dream already had the 911 patch, then the phone will already have the latest radio. Follow these instructions if the Rogers Dream did not have the 911 patch.
1. Download the latest version of the radio (3.22.26.17).
2. Rename the radio image to simply radio.img.
3. Power off the Rogers Dream.
4. Boot into bootloader mode. Hold the Camera button while powering on the Rogers Dream.
5. Connect the Rogers Dream to the computer.
6. On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
7. Type in the following command:
fastboot flash radio radio.img
8. Once finished, you can restart the Rogers Dream.
Perhaps try flashing a new recovey via fastboot?(aka screen with android skateboarding) with adb, looks at the rom bible in the dev section for more details. You also need the android sdk installed on your computer to do so, and a working mini usb cord.
ok first, you are not bricked, brick means cannot get into bootloader (camera+power) nor recovery (home+power), and it will be useless like a brick,thats why we call it "bricked" when you messed it up. Unless you use the jtag method, but thats for the super hardware geeks not for the people here in the forum.
Since you are not bricked, you can try to turn on the phone and wait for at least 5 minutes and see if the screen is still stuck on the same logo, because sometimes it takes quite long for the first boot after your new Flash. If it really stuck on the same logo for the damn 10 minutes, then you can try the following ways.
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
americanxo said:
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
Click to expand...
Click to collapse
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
my FASTboot command works but ADB cannot connect. I assume you mean I should flash the recovery, right?
alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
From where you are flashing fastboot or rom....
If you are able to go to fastboot mode, then flash the recovery from there....using fastboot from your PC....
alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
americanxo said:
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
Click to expand...
Click to collapse
Please please please do not flash rc29 on a rogers dream.. if the flash fails but installs the spl you can be in an annoying position, best unroot to the rogers firmware and root that again..
However op just needs to flash the -r version of the dream recovery.
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
lbcoder said:
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
Click to expand...
Click to collapse
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
billquinn1 said:
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
Click to expand...
Click to collapse
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
ezterry said:
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
Click to expand...
Click to collapse
Interesting stuff. I always thought there was a (carrier + hardware) reason for the different radio. Thanks for taking the time to explain.
Tried to install Cyanogen 6.1... It failed.
From there the device booted up normally on a fresh start, but I tried to recover my backup and that is where everything got all messed up.
Im stuck on the G1 screen.
Ive gotten it to the fastboot mode and Im downloading what I think I need to get my phone working again. Ive downloaded the Andriod 1.6 image from the HTC website. Do I need the recovery? I just want 1.6 until I have time to try and get Cyanogen installed.
Im currently installing JDK for the Andriod SDK.
Am I headed in the right direction?
I was using ROM Manager with Clockwork Mod. My old ROM was Super E... Not sure what version, but it was Andriod 2.1
What radio/spl do u have?
johnson8cyl said:
What radio/spl do u have?
Click to expand...
Click to collapse
2.22.19.26I
Tbry said:
2.22.19.26I
Click to expand...
Click to collapse
And spl? Do u have and eng spl? (S-off). If so u could fastboot erase your system and try to flash the rom through recovery. And fastboot flash a recovery of your choice first. Have u tried going on ezterry's thread with the new radio/spl and going that route?
Not sure what the version of the SPL is, but I know it is off. I'll check his thread out and give it a try. I might end up finding someone who actually knows what they are doing, or buying the Nexus S.
Ok. If u follow his thread exactly and fastboot flash the radio/recovery/spl u should end up with everything as described in the thread and be able to move on with cm6 with appropriate kernel. Alternatively u could boot into fastboot and open up your terminal on your computer and type in code to fastboot recovery of your choice (after it's download and put in sdk/tools folder on your PC) he has amonra link in his thread for download . Then type fastboot erase system -w (hit enter). When it's done type fastboot erase boot (hit enter). Then power down. Power back into recovery with the rom on your sdcard and flash away.
That is actually what I'm trying to do. Its just about my only option at this point.
Im having problems getting everything set up correctly though.
What are u having problems setting up?
I installed Andriod SDK, seems to be working.
Downloaded the drivers, which seems to have stopped my computer from seeing the phone.
I downloaded the Fastboot.exe, tried to run it but it cannot find ADB.dll ( Pretty sure thats what it was.)
I was basically following the steps on the cyanogen wiki.
When I have some time, I will try the Fastboot for noobs guide.
I think I followed a guide in androiddevelopers.com or something like that. If I find it again ill post a link. I don't think I ran a fastboot exe file though. Just have it in my androidsdk/tools folder. Added the variable to my paths and was good to go. Not at my PC currently though.
Edit: developer.android.com/sdk/
I believe is what I followed
http://forum.xda-developers.com/showthread.php?t=532719
Following this for fastboot.
I cannot update anything. Home + power doesnt do anything.
Only thing I can access is fastboot mode.
Fortunately my radio is up to date, so I assume my SPL is as well.
Going to attempt to try the fastboot step, once I can get the SDK working correctly
edit: I knew if I spent enough time working at it that I'd get it working.
Only problem now is getting my device to be listed.
Edit2: at first when I entered fastboot mode, I would get the "Add new hardware" for the device "Andriod 1.0"
It now says "andriod bootloader interface"
I feel like I'm so close. I'm going to keep playing with it, but what can I do to get my device listed when I type the command "Fastboot devices"?
Edit 3: Awesome. I got fastboot to work and my phone is recognized. Only problem now is getting my SD card reader to work so I can put the proper files on
Final edit: MY phone is killing SD cards for some reason. Don't know what to do
Got the SD cards to work, for some reason though, some of the commands are not working. When I type fastboot shell, I just get the usage doc.
When I do fastboot update, I get the following: error: failed to load 'update.zip'
What are u trying to do in fastboot?
Sent from my T-Mobile myTouch 3G using XDA App
Well, I fixed my phone. Back to its original state.
I guess my only question at this point my only question is if I switch to Cyanogen 6.1, will it be less buggy than my Super E ROM?
For anyone wondering, Holding home + end for about 25 seconds is what I did. From there I just went to nandriod and tried to recover the same backup that gave me the problem.
I would say no. It will not be less buggy. U can always flash and try different roms though for experiment sake. Glad u got it back up
Sent from my T-Mobile myTouch 3G using XDA App
Hi,
I bought a faulty Nexus one from ebay, thought I can fix it, as I did buy a faulty desire from ebay and was able to fix it. This time im not so lucky I guess.
So here it is:
The phone is stuck at X when booting normally.
I can access HBoot (But not Hboot USB Plug, because USB debugging is not enabled) and Fastboot USB. I unlocked Hboot. Fastboot in PC recognizes the phone but ADB does not as usb debugging is not enabled.
The phone is not Rooted
Here are my ideas so far:
Get somehow debugging on with some commands (No luck from reshearching in google)
Reflash stock rom with PASSIMG.ZIP in sdcard, but my phone does not recognize the file from my sdcard (I'm pretty certain im doing something wrong or my idea is somehow wrong)
Flash new images through FASTBOOT, but every time Signature check fails (Shipped-roms.com).
Root with superboot, but signature check failed here too.
Flash a recovery, signature check fails.
I will reguraly update my tries
Please suggest correction to my ideas or suggest new ones!
Help will be much appreciated!
I admit it, the phone might be briked, but I want to make sure that I have tried everything before I abandon this project.
And ofcourse I have no Warranty.
What file are you using for passimg.zip? Make sure it's not a zip inside a zip.
What images are you using via the fastboot flash command?
Sent from my Nexus One
You didn't unlock the bootloader, it seems - because if you did, it wouldn't be checking signatures, and you'd be able to flash anything.
First of thanks to both of you for helping.
I'm pretty sure that i do not have zip inside zip and I downloaded them from shipped roms.com -> android -> Passion-> PASSIMG_Google .... .ZIP, (Then renamed it ofcourse) Is there a difference what version of android i use?
The issue with this is, it checks the SD CARD and does not find anything. I have seen from google that the most common issue is that it starts to check the .zip file but then aborts. Does the SDCARD have to be a goldcard (I do have a goldcard but it might be faulty, right?)
I tried fastboot flash PASSIMG_Google.... .ZIP; Fastboot Flashall ( With having boot, recovery, system in my fastboot folder)
Maybe I should try to flash everything the .zip has in it seperately because that succeded for boot, system and recovery but I was too afraid to flash every partitation (Like Radio which seems to be the scariest and the most easiest way to brick phone)
For the third answer, I have ***UNLOCKED*** in bootloader in purple and top on the screen.
Once again thanks and keep suggesting!
Unpack the ZIP and flash each image separately.
Leave the radio as is, if it's updated enough (5.08 or 5.12). In any case, fastboot won't allow you to flash bad radio - and the risk of bricking the phone using fastboot is near 0.
For passimg.zip, you need to download the FRG33 shipped ROM from shipped-roms.com then EXTRACT the zip file that is inside the zip that you downloaded. Rename that file to passimg.zip
For fastboot, flash boot and system seperately.
When you boot the device normally, do you see the lock icon below the four colored x?
Sent from my Nexus One
Okay,
Did it one by one (PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip):
Succeeded:
Boot, Recovery, System and Userdata (that was only 3Kb)
Failed with signature check (Remote:Signature check failed):
Splash1, spcustom,
Did not do:
Radio
I'm going to post more details:
When booting up, it displays the X normally with the unlocking badge on the bottom of the screen and vibrates once. Then it goes black for a second or even less, the same images comes on and then it vibrates 6-7 times.
now that you successfully flashed the stock recovery, cam you boot into it?
Sent from my Nexus One
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
http://forum.xda-developers.com/showthread.php?t=710937
Thanks, Well thats it then for now, just have to figure out what to do now
Sounds like you need to get the PASSIMG.zip method to work, or unlock and flash a new recovery like amon ra, and flash a full rom with sig checks off.
siimplangi said:
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
Click to expand...
Click to collapse
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
any solution?
efrant said:
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
Click to expand...
Click to collapse
hi guys.i have exactly same situation.
does anyone have a solution fir this?
kobi_eidelman said:
hi guys.i have exactly same situation.
does anyone have a solution fir this?
Click to expand...
Click to collapse
Did you try all the solutions suggested above (passimg, fastboot flash, etc)? If yes then no I don't think so.
okay i got my hands on a nexus one slcd for $40 impecable but stuck on nexus quad color screen with lock. so i search and try various methods to restore and get this puppy up n running. bootloader unlocked nexusone pvt ship s-on hboot-0.35.0017 microp-0c15 touch-panel-synt0103 radio 5.08.00.04 jun 14 2010 i have tried various methods but all return with verification failed my windows xp reconizes it in fastboot devices and all files on here have broken links or failed verfication nbh and all that please can someone give me full update zip for 3e stock recovery
http://forum.xda-developers.com/showthread.php?t=744605
Are you unable to install recovery or anything via fastboot? I haven't dealt with a soft bricked phone but there may be ways around it. I don't know if custom hboot like blackrose would help but might be worth looking at.
http://forum.xda-developers.com/showthread.php?t=1270589
When you say its in fastboot, from your pc , following command should list your nexus
fastboot devices
Assuming this is ok, you'll need to first flash recovery
From http://forum.xda-developers.com/showthread.php?t=611829
download AmonRA recovery [do check md5sum after download]. Use command
fastboot flash recovery <recovery image name>
Confirm if you can get this to work
Yes my computer recognised the device when I typed the command fastboot devices thing is I want this phone stock with out custom recovery I don't care if the bootloader stays unlocked I boot into recovery fine it even wipes and clear cache but the system wont recover its like there's nothing there I don't know what the person who had it before me did and if they got root what I'm looking for is the original update.zip or nbh or the others but that will pass signiture verification so much confusion with amoled and slcd that I don't want to ruin my phone so please take that into consideration I have slcd sorry just in case and prefer original 3e recovery for now I just need the files even if I have to use fastboot thanks again for your interest
Have a look in the N1 wiki to unroot/restore to stock and use the PASSIMG method to get everything back to normal.
Out of curiousity, why do you want to keep it completely stock? Having a custom recovery doesn't actually affect anything on the OS side (other than allowing you to replace the OS).
Looking at your device signature "microp-0c15", it is LCD version , so yes you'll need to be careful in flasing "old" images. Try not to use any zip without knowing if it has any radio or boot image.
As far as I know using a wrong radio/boot will turn the phone in brick, so better be careful
We almost have the same specs. Only difference is the radio and mine came from Korea.
If you want to go back to stock try this one.
http://forum.xda-developers.com/showthread.php?t=1312540
If your N1 is branded, you need to make a gold card though.
Sent from my Nexus One using xda premium