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
Related
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
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.
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
I recently recieved a Nexus One that I cannot reflash at all. It simply will sit at the static X logo upon boot. I can still access the bootloader. Recovery does not work at all. I have tried to wipe and restore using fastboot, and whenever I try to write any images, they seem to push to the phone (progress indicator on phone fills up, etc) but I never get a finished message on the computer. I let it sit for half an hour before I gave up on it and pulled the battery. I have tried this with Windows 7 on a desktop and a MacBook Pro, using various different USB ports and cable combinations on them. I cannot do the PASSIMG.zip method either because the phone never seems verify the FRG83 image but will never offer me the Yes or No dialog to write out the files. It kicks back to the regular bootloader options.
Is this Nexus One bricked? Can I bring it back from the next-to-dead? Am I really just missing something obvious here?
By the way, have you unlocked the bootloader? Using fastboot to push anything requires unlocked bootloader.
The bootloader is unlocked.
Ok well this might be a stupid question but you said you were using windows 7 and with windows the extension is hidden so if you name the file passimg.zip it will actually be named passimg.zip.zip and the phone won't recognize it so try naming it passimg
Also for the passimg method did you try using the frg33 file instead of the frg83 file.
I have Windows set to show all extensions regardless. I would say I'm plenty savvy when it comes to computers, just not Android (yet )
I tried both the FRG33 and FRG83 files. They just don't seem to do anything. The phone seems to check them: It says that it found the PASSIMG.zip and the progress bar in the upper right slowly fills up. Once it fills, it sits for a second and just kicks back to the normal bootloader choices as usual.
Thank you for all the quick responses! I hope I can fix this Nexus One. It's practically in mint condition...
It's strange that the bootloader is unlocked but you can't flash any ROMs :/
When you say that recovery doesn't work at all what exactly do you mean by that? When you boot into recovery what happens?
Now since we talked passimg I doubt it will work more than the others but did you try the GRI40 file?
I cannot seem to find a GRI40 that can act as a passimg. And when I say recovery doesn't work at all I mean that I just proceed to the the static, non-moving nexus logo and it doesn't ever proceed past it. I have tried to use "fastboot boot recovery.img" with a ClockworkMod and Amon_RA image and it seems to upload to the phone but I just end up with the nexus logo.
It seems that I can fastboot erase the userimg and cache, and get results that are expected. When I fastboot flash anything it sends to the phone but the phone never seems to do anything with it past that point.
When it gets stuck on the static X logo do you get 7 vibrations?
Did you try and fastboot flash Amon-RA then try and reboot into recovery. And for the GRI40 file it's on htc's developers web site http://developer.htc.com/
I only get one vibration. I tried to flash Amon_RA and reboot but it's like the flash never completes. I don't get anything different.
same issue here and browsing since yesterday for a proper solution and not yet !! any brave ideas ,pls share!
OverdrivenCore said:
I only get one vibration. I tried to flash Amon_RA and reboot but it's like the flash never completes. I don't get anything different.
Click to expand...
Click to collapse
Try fastboot erase to erase everything on the phone then flash fresh recovery
Sent from my Nexus one using xda app-developers app
Kind of in the same boat, opened a thread my self but none of the suggestions are working. When im in fast boot it freezes for a second a runs a quick check. I just about catch it saying wrong passimg image or something along them lines.
Sent from my GT-I9100 using xda premium
Hi all,
I have a Google Nexus One which I had rooted a couple of months back (just root and no boot loader unlock). Everything was fine and I had factory restored it successfully once in the due course.
The problem was when I did a factory reset again yesterday so that I can sell it, there was a boot loop. I tired everything like restart, stock restore again from recovery, battery removal but all went vain. Fortunately I tried connecting via USB and thus I escaped from boot loop but still I was stuck there. None of the 4 system keys didn't work.
I just sat researching on Google and at last got the reason for the strange behaviour on the otherwise 2 year old not a single glitch ever phone. The issue was the with the stock Launcher apk. Just then I remembered that I had uninstalled the stock Launcher given the root access and so confident on the Holo launcher.
Again some researches and I came to know I can install (or "push") the launcher using the 'adb' command. I booted into recovery console, connected my phone to Windows 7 PC and installed the driver to get the phone detected. But when I typed 'adb remount' it gives 'error: device not found'. This is where I'm stuck now and since Googling didn't provide anything worth I'm back to my favourite tech forum.
Hope you got it clear here and someone can help me.
Regards,
ursJAR
Sent from my Galaxy Nexus using xda app-developers app
PS: And why is typing on the xda android app so terribly slow??!
Stock recovery doesn't allow ADB access.
Since you did factory reset - ADB isn't running on the phone either.
So you can't recover from this situation without unlocking the bootloader. Unlock it, install custom recovery, adb push the launcher through it.
Forgot to mention - I'm not suggesting PASSIMG, since your phone is likely updated to the latest, and all the PASSIMG are from older builds. You could try, though - if you don't want to unlock the bootloader, Korean PASSIMG might be what you need. See N1 Wiki, section "Unroot/restore", PASSIMG method.
If the boot loader is unlocked, I believe there is no way to revert to the fresh situation.. right?
Sent from my Galaxy Nexus using xda app-developers app