Database Develop

Issue w/adb showing no device yet fastboot shows serial

I have been trying since yesterday to get my Nexus back in to working function. I had CM 6.0 with ClockWork recovery. Through recovery I wiped data/cache/etc then attempted to flash a stock frf91.zip from the sd card. As it was in the process of doing so recovery gave me an error and said it would reboot into Rom Manager. Now my phone hangs on Nexus X logo before the boot animation. I can power the device into fastboot to choose bootloader-reboot-reboot bootload-power off.
I believe that recovery process had the error/issue right after it deleted the system image.
YET I do not have the function of my Power/Multi-Use Button on the top of the phone. So I tried to use adb (which I have used with my phone previously without any issues) to attempt to install the stock rom image.
With adb running I sent the command to display the devices connected. It shows the list but with nothing connected (NOT an error or no devices connected), just blank. I then tried fastboot and sent the command to list connected devices, fastboot showed my devices serial as a connected device.
I was able to flash a system.img file using fastboot yet nothing happened, an all other restore attempts, like userdata.img or boot.img, etc. will not work and come back with a error of no remote permission.
Sorry for the entire book, but I am sort of lost.
My reason for this whole mess is because I wanted to restore my phone to a stock rom and recovery to send it in to have the power button fixed while retaining my warranty (my bootloaded IS locked).
When I get home from college today I am going try loading a stock factory passimg.zip of ERD79 on my sd and let fastboot try to pick up on it. I really have no other option haha.
Anyone have a suggestion? Honestly I am willing to just send it in AS-IS or brick it an tell them I had no idea what happened that I couldn't use the power button and it died after an update.

I see that no one has any idea really haha.

Couldn't tell from reading your write up - can you boot into recovery?
Sent from my Nexus One using XDA App

no I cannot. I do not have use of my power button. I am going to read through the new thread concerning accessing recovery without use of the power button.

To use adb, you need to be in recovery, or fully booted with debugging enabled.
To use fastboot, you need to unlock your boot loader.
Try reverting to stock via passimg method (one of the newer ones, if you have the Froyo radio).
Sent from my Nexus One using XDA App

I recently realized that was the issue with adb. So fastboot is out of the question then. Doesn't the passimg method require use of the power button though?

Unroot/Restore (use passimg method):
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App

hboot scrolls quickly when I try this and I catch that it says that is not a valid passimg.img
any ideas?

Should be passimg.zip (not img).
Makes sure it's not a zip inside a zip.
FRG83 seems problematic, so try FRG33 instead.
Sent from my Nexus One using XDA App

Just discovered this gem:
http://forum.xda-developers.com/showthread.php?t=825909
Sent from my Nexus One using XDA App

I got the passimg method working correctly. I mean passimg.zip in the previous post. I tried frf91 and it went through then said checking and went straight back to hboot without asking for permission. I'm going to try frg33 and if that doesn't work I will try the app you found.

frg33 seems to be working

hboot with FRG33 worked and the phone booted up with rom. thank you very much for all of your awesome help danger-rat.

No worries...
Sent from my Nexus One using XDA App

[Q] Nexus One stuck at X/ No recovery

First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.

Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk

Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on

No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.

Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.

fastbook oem unlock
install Amon RA recovery
flash new rom.

Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.

From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.

[Q] Reviving my N1

Back when 2.2 first rolled out OTA I've had issues with my phone, it's been dead
It's not rooted or unlocked, was waiting for 2.2 to do all that
when the OTA came up, I had the phone install it
never booted up fully, would stick at the flashing Nexus logo till it locked up completely
now it can't get past the static Nexus logo at all
when attached to my PC it will not show up in ADB devices
I can get into recovery and the bootloader and it can access files on the SD card
what can I do to get something loaded on it so I can root it and move on with a custom ROM?
At one point I did have a file that loaded called PASSIMG that reset the phone to original shipping, but for the life of my I can't find it again, if I can get a hold of that file be it 2.1 or 2.2 based I can do what I need, or are there any other options?

http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Extract the .zip from it, rename to passimg.zip, put it on the root of your SD card, boot into HBOOT and you should be back in business, it will OTA itself up to 2.2.2 in no time.

Read my signature, find there "Unroot/restore" guide.

Something's not right, I have the file in the SD card, boots into HBOOT
Reads the SD card,this step is fairly fast, then does nothing else
This has me intrigued now.
Tried two different files, it is extracted and named PASSIMG.zip
Not sure what else to do

Double check the file isn't named passimg.zip.zip common thing.
Or if you can't be arsed fiddling, unlock bootloader, extract the system.img and boot.img files from the passimg, and use fastboot to flash them.
Ps. You have tried to wipe it since it broke, right?

You don't need to extract anything. Just try to actually read the guide carefully and execute step-by-step, before posting additional questions.

Thanks Jack_R1 finally got it sorta working, it flashed the file over fine but is now stuck on the static Nexus logo for close to 20 minutes and seems to be doing nothing, gonna try again with an older ROM instead of FRG33, which one did it ship with originally?

Stuck on static Nexus logo - might be a faulty SD card, for example.
FRG33 should definitely work, the older that worked would be FRF91, but you won't be able to flash it using PASSIMG once you have flashed the FRG33 - it won't allow to downgrade.
If you can get to recovery (power off, press and hold trackball, power on) - perform a factory reset, remove the SD card, and try to boot again. If it doesn't work - you might consider making things easier on yourself and using fastboot oem unlock.

Jack_R1 said:
Stuck on static Nexus logo - might be a faulty SD card, for example.
FRG33 should definitely work, the older that worked would be FRF91, but you won't be able to flash it using PASSIMG once you have flashed the FRG33 - it won't allow to downgrade.
If you can get to recovery (power off, press and hold trackball, power on) - perform a factory reset, remove the SD card, and try to boot again. If it doesn't work - you might consider making things easier on yourself and using fastboot oem unlock.
Click to expand...
Click to collapse
Not the SD card, works fine on my other phone
Can't unlock, phone not showing when doing a ADB Devices
Thinking it might be bad memory on the phone

To use adb, you have to be able to boot the phone to some level, and you may not be getting there...
Boot into bootloader, switch to the fastboot screen, then try fastboot devices.
You need fastboot to oem unlock, anyway, not adb (if you're planning on taking that route).
Sent from my Nexus One using XDA App

You use fastboot to unlock, not ADB

Yep, got it going now, not sure why I assumed that if it wasn't coming up under ADB, that fastboot would not work.

grats!
It 's alive! :d

[Q] Urgent: Nexus failing to boot

Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.

Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.

Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!

Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.

Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!

Confirmed - Dude is giving you good info... xD

Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.

Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?

Use the FRG33 image

Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?

Try the passimg, but it's possible that you are looking at hardware failure...

ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.

Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.

According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?

None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.

Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.

If it's running, you can try to pull a log, and see what error reports you get?

andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.

So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?

Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks

Fastboot.exe has stopped working - Phone Corrupt

Hello my lovely Nexus family,
I need your help! I've searched all over the web and these forums, and have yet to find a single thing that would help me.
After making a stupid mistake from tinkering, my phone was stuck on the "Google" screen. Not a big deal, just a simple wipe and fresh flash (and yeah, that's what I wanted anyways), right? So I went straight to Wugfresh's Nexus Root Toolkit to full wipe. It did the whole process of flashing MRA58R to the phone until I got to "sending sparse 'system'" on the terminal window. "Fastboot.exe has stopped working. Windows is finding a solution....." suddenly appeared while the terminal was processing everything. When the phone decided to reboot after thinking it had finished, it came back with the "Phone Corrupt" message.
I don't know what to do, as this is the 9,999th time I've flashed a phone, and I've never seen this before (obviously) so I'm not really sure what to do.
If I'm missing any details, which I feel I am, do not hesitate to ask.

May be obvious no... But you didn't actually say...
Will phone boot into fastboot if you have it powered off, the first pressing and holding volume down, then pressing and holding power until the phone boots?

scryan said:
May be obvious no... But you didn't actually say...
Will phone boot into fastboot if you have it powered off, the first pressing and holding volume down, then pressing and holding power until the phone boots?
Click to expand...
Click to collapse
Yes, I'm able to boot into fastboot with the phone powered off using the physical buttons. I'm also able to get working commands from the terminal.

Then what is the issue? Flash The image manually, re-install fastboot if needed... Or better yet download the image from google manually, check MD5, extract the main zip, as well as the update zip inside... using the fastboot that comes with it to flash all partitions?
One flash went wrong... So ok try again. And don't use the toolkit so you can actually follow whats going on (and because the only posts with troubles seem to be from people using toolkits)

scryan said:
Then what is the issue? Flash The image manually, re-install fastboot if needed... Or better yet download the image from google manually, check MD5, extract the main zip, as well as the update zip inside... using the fastboot that comes with it to flash all partitions?
One flash went wrong... So ok try again. And don't use the toolkit so you can actually follow whats going on (and because the only posts with troubles seem to be from people using toolkits)
Click to expand...
Click to collapse
I've done more than one flash today. My next will make 20 in the same hour with failed results. I'll try flashing the bits of the file manually and see how that works.
It could even be the computer I'm using. I'll report back soon.

Are you using the same fastboot.exe every time and getting the same error? Did you verify MD5

So, I got home, hopped on my laptop and got to work as usual. I used the factory provided cable and the problem was solved. I believe it has something to do with either the cord I was using to transfer the data, or the computer I was using.
Other than that - PROBLEM. SOLVED.

If the fastboot exe was fail ("stopped working") the cable was less likely the issue, most likely just the binary on that computer.

Perfect example of why not to use a tool kit until "after" you know how to do it manually.