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
Related
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.
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 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
attempted root and used superboot grj22 from modoco pphone is unlocked and after double clicking on indows bat file as directed phone is locked on boot x
this phone has just come back from htc with a new power switch installed and 2.3.4.
anyway could use some help daughter is upset I locked her phone.
can get to boot menu however can not get into recovery. I get a triangle with exclamation in it
thanks
Please read the Wiki, Rooting guide for unlocked bootloader.
Flash recovery through fastboot.
Flash whatever ROM you want from recovery.
You've flashed a wrong kernel (which is contained in "superboot"), that's why you can't boot.
another question
read wiki and followed instructions which said after loading passimg that this was an older version. searched more and found another thread that gave a new file that was supposed to load the older version of the rom and get around the error "older version"
still not working any other ideas will be appreciated
Just to make sure I understand right you tried the frg83 passimg file and you got "main version is older" error? If so then can I just ask you is your bootloader unlocked (at the X screen before the cyanogen mod logo do you see an unlocked padlock)?
hi
yes padlock on screen is unlocked tryed to flash again and get the same error version is older
thanks for trying to help kid leaves for school tonight and is freaking
more
also askes if I want to reboot device
It'll be long fixed by then don't worry
Boot into bootloader then from there select the recovery option. Once there tell me what you see if you see and android with a /!\ next to it then press power and vol+ power slightly before. Then you will get a menu select power down. If you go straight to the menu tell me what color the writing is.
hi
get the triangle white with a orange exclamation in it
Ok then you'll need to flash a recovery via fastboot. So since you bootloader is unlocked I assume you already have the SDK set up and the drivers installed if not then I can help you with that too, but now just download this file and place it in the same directory as fastboot on the computer and download this file and put it on the root of your sd card (not in any folders).
Then boot the phone into fastboot (hold down the trackball while powering up) then connect the phone to the computer via usb and open a command prompt in the directory where you have fastboot. Then input these commands:
fastboot devices (this should return the s/n number from your phone)
fastboot flash recovery recovery.img (where recovery.img is the name of the first file you downloaded earlier)
fastboot boot recovery.img (same thing here)
The phone should then boot into recovery from there use the trackball to navigate go to flash zip from sd card then chose zip and chose the second file you downloaded earlier (the one you put on the sd card), after that wait for it to flash then press vol- to go back to the recovery main menu then select reboot system now and your all good you have stock with root access, if you want to flash a custom ROM then just ask I can explain that too.
As I've said, follow the guide FOR UNLOCKED BOOTLOADER.
You didn't.
The guide for unlocked bootloader is in Unroot/Restore section, called "using fastboot".
Actually, the only thing you need to do is to install recovery. Go to "recovery" guide - again, FOR UNLOCKED BOOTLOADER - and install Amon_Ra's recovery.
Once you have it, you can flash whatever you want, including stock ROM.
ok
everything is good except that i tryed to flash downloaded zip from sd and got error that zip is signed wrong also zip verifacation failed
again thanks excited I got this far.
so after this gets fixed than will phone reboot and go to 2.3.4 that was on there before?
will I be good to go for a new rom and last but least like the miuis and recommendations from an expert?
funny I bought the sensation and forgot how to do all this probably the pressure of the child (oh my god you wrecked my phone) Forgetting of course it was dads to begin with DARN KIDS
me dumb as a box of rocks toggled zip verifacation and ra unzipped.
afraid to push any buttons.
should I reboot?
and then Its ok to load a rom?
thanks
radio should be ok as it was just loaded from htc?
Ya you should be good don't worry you can't brick it by flashing something to the system partition only to the recovery and hboot partitions. Just select reboot system now and all should work fine.
Sorry for the late response I was away from my computer
still stuck on nexus x screen ??
earlier someone posted that when I used superbot I got the wrong kernel?
not sure but still stuck
just tryed to boot into recovery and it wouldnt go
Oh right sorry forgot an important step you kind of need a ROM my bad ok so forget about su you're going to need to flash a ROM I suggest cyanogen mod as a first ROM but it's up to you if you want miui or something then go for it. Here's a link to cm7 http://dl.dropbox.com/u/31690913/android%20files/update-cm-7.0.3-N1-signed.zip
So to flash this simply boot into recovery then go to wipe, wipe all at least 2X I do 5X to make sure then just go to flash zip from sd card and flash the ROM.
In that case do like we did last time and reflash it through fastboot. Now sorry but I gotta go maybe someone else can come and help you if not I'll be back later tonight.
thanks
thank you so much for helping me with this got everything working including the new miui rom.
when you panic just a little you forget all the things you knew how to do before.
thanks again.
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
picante544 said:
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
Click to expand...
Click to collapse
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
sphinxcs898 said:
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
Click to expand...
Click to collapse
picante544 said:
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
Click to expand...
Click to collapse
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
http://theunlockr.com/2012/10/16/how-to-root-the-htc-nexus-one/
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Resolved--hardware problem--trackball
Coincidentally, another user had a very similar experience with his N1 at the same time. He determined it was his trackball. I tore my phone apart, disconnected the trackball and the phone now works again.
Thanks again to those two people who responded.
sphinxcs898 said:
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Click to expand...
Click to collapse