Database Develop

[Q] Bricked my CEll upgrading the radio

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.

Fastboot and recovery images

Hi there, I am trying to figure out what the difference between fastboot and recovery images are? It seems to me that you can flash images and radios when you are in fastboot, so what is the point of running recovery images?
Also, is the recovery image something that runs ontop of fastboot?

Read the wiki.

Know-Fear said:
Read the wiki.
Click to expand...
Click to collapse
Neither the android 101 section nor the Nexus one/ Recovery images section of the wiki contain any information as to the differences between the 2 or how the recovery image loads, perhapes you can add that into the wiki?

Basically, I would say the biggest difference is functionality...
Fastboot has very limited "on board" options, but you can do a bit more when connected to a computer, and even more with an unlocked bootloader. You're pretty much limited to flashing images normally, and the unlocked bootloader allows you to also flash unofficial images. If your phone won't boot into the system or recovery, then fastboot might be your only option.
Recovery has more "on board" options, especially with the custom recoveries, where you can flash images, make and restore backups,and also create and format partitions (among other things), directly from the phone. Connected to a computer gives you a bit more flexibility, but not much (using adb to push apks direct to the phone, whereas from recovery on the phone, you need a flashable zip).
I do pretty much everything from my phone, since I'm not always near a computer. That means I rely on recovery and the terminal emulator for the most part. Once, I needed to hook up to the computer and use fastboot to flash a new recovery, because every other optiod failed...
For me, having a custom recovery is much more useful than unlocking the bootloader. Unlocking the bootloader just makes it a lot easier to install a custom recovery. I would even venture to say that most people go direct to installing a custom recovery after rooting, or after unlocking the bootloader. Even though you can install ROMs through fastboot, it's much easier to use recovery.
The other big difference is that unlocking the bootloader will wipe the memory, whereas rooting and installing a custom recovery won't erase your memory...

I see, thanks for explaining to me the differences, but does anyone know where the difference comes from??? Does the recovery image run ontop of fastboot and call functions from fastboot to achieve its backup options or what??? If not, could you simply remove fastboot to save memory and be left with just the recovery image which persumably has more functions anyways?

There's a bit of mis-information in this thread.
Fastboot is a binary that you execute on your computer. To be able to use it, your device needs to be booted into the bootloader. There is no "fastboot image". Most fastboot commands require an unlocked bootloader. The most used fastboot command is "flash" which lets you flash images to any of the partitions on your device.
A recovery image in the recovery partition is like a mini ROM which allows you to perform some tasks directly from that partition without booting into your ROM, like applying updates to your ROM and performing backups. Custom recoveries have more functionality than the stock recovery. To enter the recovery partition, you need to boot it through bootloader (generally).
adb is another binary that you execute on your computer. It is unrelated to fastboot. It allows, among other things, transfering of files to/from your device and running a shell.
flash_image is binary that you execute on your device, or on your computer using a shell (via adb). It allows you to flash images to most of the partitions on your device. This binary requires root access.

I see, thank you very much for clearing up this misunderstanding. I take it both fastboot and recovery images manipulate the bootloader to achieve flashing and backup capabilities? Since on default the USB support is disabled on the bootloader, which is why you need to unlock the bootloader first so that the fastboot can send its signals to the bootloader via USB. Since recovery images can directly manipulate the bootloader without the need of a USB, therefore you can do not need to unlock the bootloader to use recovery images.

xcmir said:
I see, thank you very much for clearing up this misunderstanding. I take it both fastboot and recovery images manipulate the bootloader to achieve flashing and backup capabilities? Since on default the USB support is disabled on the bootloader, which is why you need to unlock the bootloader first so that the fastboot can send its signals to the bootloader via USB. Since recovery images can directly manipulate the bootloader without the need of a USB, therefore you can do not need to unlock the bootloader to use recovery images.
Click to expand...
Click to collapse
I think you need to re-read my post.
1. There is no "fastboot image", so I don't know what you are talking about there.
2. A recovery image does not "manipulate" the bootloader.
3. USB support is not disabled on the bootloader.
Sent from my Nexus One using XDA App

efrant
Can you explain the bootloader a bit more?
The bootloader has two very similar screens. The only differences between the two screens are the four menu options, and one screen is labeled HBOOT, and the other FASTBOOT. I assumed these to be be two operating modes of the bootloader, since the fastboot binary will only work when the phone is at the FASTBOOT screen, and not the HBOOT?
How do you refer to, or distinguish between, these two "modes"?
Also, the screen labeled HBOOT has four menu options, the first one being FASTBOOT, which merely takes you to the second screen with the FASTBOOT label.
So, just for giggles, let's call the first screen/mode/thingy HBOOT, and the second FASTBOOT...
It's my understanding that the fastboot binary communicates with the FASTBOOT 'thingy' on the phone (both parts are known as fastboot). This is similar to the adb binary communicating with adbd on the phone...
Now, with that in mind, the OPs original question seems to be related to interfaces on the phone. Wouldn't it then be fair to assume that these two interfaces we're the recovery and the FASTBOOT 'thingy' (although I actually believe he was referring to the bootloader as a whole)?
Sent from my Nexus One using XDA App

danger-rat said:
efrant
Can you explain the bootloader a bit more?
The bootloader has two very similar screens. The only differences between the two screens are the four menu options, and one screen is labeled HBOOT, and the other FASTBOOT. I assumed these to be be two operating modes of the bootloader, since the fastboot binary will only work when the phone is at the FASTBOOT screen, and not the HBOOT?
How do you refer to, or distinguish between, these two "modes"?
Also, the screen labeled HBOOT has four menu options, the first one being FASTBOOT, which merely takes you to the second screen with the FASTBOOT label.
So, just for giggles, let's call the first screen/mode/thingy HBOOT, and the second FASTBOOT...
It's my understanding that the fastboot binary communicates with the FASTBOOT 'thingy' on the phone (both parts are known as fastboot). This is similar to the adb binary communicating with adbd on the phone...
Now, with that in mind, the OPs original question seems to be related to interfaces on the phone. Wouldn't it then be fair to assume that these two interfaces we're the recovery and the FASTBOOT 'thingy' (although I actually believe he was referring to the bootloader as a whole)?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
As far as terminology goes, this is what I have read (and which makes sense to me): 1) the bootloader is the white screen with the three androids at the bottom. Yes, there are two screens, but so? It is just a menu in the bootloader, just like a menu in a ROM. It's the bootloader. 2) Fastboot is used to refer to the executable, not to the fastboot menu on the device.
Yes, I supposed you could consider a recovery an "interface", just like a ROM is an interface. Would I compare it to fastboot? Not really. Fastboot and adb are two interfaces to interact with your device from your computer. The ROM and recovery are two "interfaces" on your device itself...

Fastboot, or actually bootloader, is the part of the phone that loads when it's powered on. It also happens to have PC interface through USB and "fastboot" executable.
When it loads, it either allows user control or loads one of the bootable partitions. One such partition is ROM. The other is recovery. In fact, recovery is a small ROM with features for controlling the phone - flashing images etc. You might as well write a custom recovery that will allow you play Tetris. It's just another (but very small) ROM.

Help! Stuck at HBOOT, need ideas/help!

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.

soft bricked

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

[Q] developer screen??

ok, so I used the all-in-one tool kit (from the development area) to root my phone. The CWM went fine. I tried to flash the explosion rom (developers area again) and when it rebooted it went into the "development purposes only" screen. I can boot into bootloader and access the hboot and fastboot options. I tried going into recovery and factory reset, but it just reboots into the developer screen again. Any advice on how to remedy this is greatly appreciated!!!
Thank you

Missing customize/mns and cid folder, flash other rom to fix.

desirech4cker said:
Missing customize/mns and cid folder, flash other rom to fix.
Click to expand...
Click to collapse
I hate to say it, but can you dumb that down a bit... I am a bit of a noob

.
Dumb version: the dev that made the rom removed folder mns and cid folder to remove htc sense stuff which is needed for htc framework, or has some missing values in the xml, if you still don't understand ask it in the explosion rom thread about the bug.

desirech4cker said:
.
Dumb version: the dev that made the rom removed folder mns and cid folder to remove htc sense stuff which is needed for htc framework, or has some missing values in the xml, if you still don't understand ask it in the explosion rom thread about the bug.
Click to expand...
Click to collapse
ok, thanks., I clicked the button for ya. So, I got the why it happened, still not sure what to do now. I did the CWM before, but now when I try to boot to recovery, it kicks me back to the "developer screen." I've tried redoing the CWM, but still can't get into it, so I don't know how to wipe everything and/or flash a new rom.

Connect phone to usb turned on even it's on developer screen or on homescreen type "adb reboot recovery" in windows cmd, be sure your on adb folder when you used to unlock your bootloader.
Then it will shut off and be in recovery, if still can't go to recovery reflash recovery.img typing "fastboot flash recovery recovery.img" in bootloader mode, then go back to fastboot and choose recovery.

desirech4cker said:
Connect phone to usb turned on even it's on developer screen or on homescreen type "adb reboot recovery" in windows cmd, be sure your on adb folder when you used to unlock your bootloader.
Then it will shut off and be in recovery, if still can't go to recovery reflash recovery.img typing "fastboot flash recovery recovery.img" in bootloader mode, then go back to fastboot and choose recovery.
Click to expand...
Click to collapse
rebooted to recovery, kicked back to "dev screen", flashed recovery.img (cwm), successful. Returned to bootlloader, clicked recovery, kicked back to "dev screen." Any other ideas? I don't know if I can click that button multiple time, but I'm going to try and I really appreciate your patience.

Ok, So I played pissed off retail customer and got them to replace my phone... Love it...
Anyways, I just had one question before I risk tanking another phone. I know a lot of people run GSM, but mine is CDMA, can I root, and run the unknown rom as laid out in the noob guide in the general discussion area? or was that part of my problem in the first place?

gsxrrocker said:
Ok, So I played pissed off retail customer and got them to replace my phone... Love it...
Anyways, I just had one question before I risk tanking another phone. I know a lot of people run GSM, but mine is CDMA, can I root, and run the unknown rom as laid out in the noob guide in the general discussion area? or was that part of my problem in the first place?
Click to expand...
Click to collapse
You could do it but I think you might lose access to your network because of the different radios but I'm not 100% sure.
If you are gonna try tho you should probably make sure you have a ruu for your network (if you can find one) so you can flash it back if anything goes wrong.
Sent from my HTC Desire C using xda app-developers app

You can't flash roms bcoz it's all for GSM that's why you got problems.

gsxrrocker said:
ok, so I used the all-in-one tool kit (from the development area) to root my phone. The CWM went fine. I tried to flash the explosion rom (developers area again) and when it rebooted it went into the "development purposes only" screen. I can boot into bootloader and access the hboot and fastboot options. I tried going into recovery and factory reset, but it just reboots into the developer screen again. Any advice on how to remedy this is greatly appreciated!!!
Thank you
Click to expand...
Click to collapse
Wait...how did you gain root and what recovery were you trying to flash that ROM with. My CDMA Desire C will not root or boot into recovery. The superuser script requires you to be able to boot a custom recovery to flash it...and all I get is the developer screen error like you. AI have posted for how to find info on building a recovery for the CDMA version, but noone has responded. And there are no sources for our CDMA version listed, which I complained to HTC about. But they misunderstood my complaint as a complaint that we were not upgraded to JB yet...dummköpfe