Database Develop

[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.

ROM Manager no boot loader

Hi,
Full version as a note. Droid 1
Flashed clockworkmod recovery (2.5.0.1), went fine. Made a backup of stock rooted ROM, worked fine. Next flashed bugless beast .6, while clearing data & cache, no problem.
Now i want to flash to cm - trying out different ROMs - trying to reboot into recovery or flash another ROM both fail to get me to a bootloader. Instead i see the motorola boot logo for 30-45 seconds, followed by what looks like a regular boot (motorola M, then Droid eye, & booted.). I have also tried fixing permissions.
If anyone has any idea why this is happening or can direct me to a forum link it would be greatly appreciated. Sorry if this is in the wrong section, and yea I've tried looking through the forums for a while.
Thanks

just a little baby sized pump...

This happened to me too after working perfectly for several months. All of the sudden I just couldn't get to clockwork. I am running CM7 Nightlies. After not being able to fix the issue for several days I decided that a full wipe via the .sbf method was in order. I've got everything up and running again but it was an annoying process. Can anyone out there help us to understand why this happened so we don't have to deal with this again?

Do you have a link for the method you described about? That would be really helpful!

An ever so slightly larger bump
I really am not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.

And possibly solved..
One: Please pardon my ignorance, doing these things on my Eris was far easier, or at least what I got used to.
Two: Please also ignore the word boot loader in my previous posts, as it was the recovery console that I could not get to load. Sorry Again.
Three: Its magically working. My methods were unscientific to say the least, but the Droid is now in "ClockworkMod's Recovery v2.5.0.1".
Things I finally did:
NOTE - I DO NOT BELIEVE ANY OF THIS TO BE THE PROPER ORDER OF THINGS. PLEASE VERIFY WITH SOMEONE FAR MORE INTELLIGENT THAN ME. THE FOLLOWING REFLECTS THE PROCESS I DID, AND SHOULD PROBABLY NOT BE FOLLOWED UNLESS A MOD ACTUALLY SAYS THIS WAS CORRECT
1. Pulled Battery, hold power button down for a few seconds, and then put back in
2. Hold Up on D-pad while holding the Power Button
3. You see the following
Code:
bootloader 2c.7c
battery ok
ok to program
connect usb
data cable
4. Connect USB data cable to PC running RSD Lite. You will also want a .sbf recovery file from a trusted source.
5. Select the .sbf in RSD Lite. Tell it to start. I used the clockwork recovery only .sbf
*** Where things got officially weird for me ***
6. The .sbf file I told it to load seemed to work, as the progress bar moved. The phone almost instantly rebooted, back to the ROM I was running minutes earlier. Clockwork had not been working previously trying to reboot into recovery, but almost instantly upon trying this time, I was in recovery mode.
NOTE - The USB cable was still plugged in as well. I don't know which combination of things actually got this to work, but it did.
Hope this helps someone else out.

USB/Charger reboot the phone, download mode lost, vibrant rom on i9000

OK guys I really badly need some help. My phone is in a non-workable state and I am starting to run out of options.
I did some mistakes but I will try to take out the details to list mostly the fact, hoping someone will take the time to give me directions.
- I have a galaxy s I9000 (switzerland/orange)
- I had upgraded to 2.2 via Kies.
- I got tired of the phone becoming increasingly slow. I found out about voodoo lag fix. I read 3000 forum posts, documentation and stuff, and when everything seemd easy enough, I installed voodoo via Odin.
- Here problems started. After installing voodoo, the phone booted, but the robot voice said "convert data partition. Not enough space on partition". Then again. And again. It was stuck in a boot loop. This problem doesn't seem to be documented anywhere i could find. The only instructions I could find on how to disable voodoo were to create some files on the disk, not very helpful when you can't boot the phone.
- I found a couple of threads with people who had the same message, and the advice their were given was to flash another rom.
- So I went to samfirmware.com and downloaded 2.2.1 for I9000 (JS8). I installed it through Odin. The phone booted, showed me the Galaxy S screen, then went black. Then it would vibrate every 20 seconds or so. Once, then 3 times in a row. I waited 30 minutes because in some places it said that may take long, but the situation didn't change. I rebooted, tried again after taking about the battery, wiped data, reset factory settings etc. The phone state wouldn't change, and I started to get a little desperate, because this was a stock rom, and if that didn't work...
- I read 3000 more threads, and phone a guy who had been in this situation, and got out of it by first installing "Eugene's JK2 froyo that never bricks" and then after wards reinstalling the stock rom.
- So I installed Eugene's rom. I knew it was trouble that it was a vibrant's rom, but I figured, I had read everywhere that as long as your phone supported download mode you could still always re-flash a new rom, so I decided give it a try.
- And the phone booted. Asked my pin, loaded stock android and all. I was happy at first, but then new trouble came. Now, whenever I plug in the USB, the phone's screen goes black after 4-5 seconds. When I unplug it, phone reboots. No charging battery appears when I plug the turned off phone on the charger.
- And worst of all, the buttons got mixed up. Vol up is vol down now. But more of a problem, 3 button recovery and 3 button download mode don't work anymore. I couldn't find a way to get them back. So I can't flash a new rom with Odin :-/.
- My latest was to install rom manager since I can access the market. I downloaded the tedgy rom. Installed the "clockwork recovery mode" from Rom Manager. It asked me if I had I9000 or vibrant, wasn't sure what it expected since I have now a vibrant rom on an I9000, but I put in I9000. Then I reboot telling rom manager to install Tedgy. I get a recovery mode screen which offers to reboot/reinstall packages/wipe data, then does a couple of operations, and finally gets stuck on :
can't open /cache/update.zip
(bad)
installation aborted
So there I go, with a vibrant rom on my I9000 (rooted, at least), a phone that can boot a half-functionnal android, but with a useless cable plug, an unchargeable battery, and a download mode I couldn't find... And waiting for my wife to get back with her phone so I can charge my battery again...
Any help or lead to help me get another rom installed on this phone again would be *greatly* appreciated. What other ways do I have to access download mode ? Or is there a way to get to it despite my buttons being messed up ? Maybe the rom manager issue can be fixed ?

OK well I got out of it somehow.
In case someone else had this same issue, here's how I got out of it :
1) Install ADB.
2) launch Odin
3) go to adb folder in command line and type "adb reboot download" but no enter just yet.
4) plug the usb cable on the phone.
5) type enter in the adb shell in the small window of opportunity you have before the screen goes blank. This reboots the download mode and allows new flashing via odin.

Any answer for this thread?
Did you fix the problem?
I'm stuck with the same case...

Help! I need to get back to stock rom on droid bionic!

Dear Sir/Madam,
Before Spring Break, I rooted my droid bionic using motofail for windows. I do not know what the software version is, but I will include the software (motofail) in this email. On Thursday March 28, 2012 I decided to try installing ROMs to my Droid Bionic. I saw that Liberty Rom, Blurr3d Rom, and Eclipse Rom were cool roms. so first, I got Bootstrap (I will include it in this email) Bootstrap is a .apk file. I also got ROM manager, titanium backup, and one more, but i do not recall what it was. I made a backup of the stock ROM with ROM manager. and i installed bootstrap. little did i know that if something bad happens to the phone during a ROM install, you cannot restore a previous backup. So i cannot get my stock ROM back on. later on, before i had a problem with bootsrap i installed liberty ROM. then i got board with it then got blurr3d. then i got eclipse ROM. that's when i started to have problems. After i installed the eclipse ROM, noticed that i could not get any cell service or data service. I could get data from wifi though. So i freaked out and got liberty ROM. i read up on it and someone said i should get safestrap. Safestrap is like bootstrap but it is safer because you can access the recovery menu from boot and not have to access it through an application on the phone like with bootstrap. So after i got safestrap i installed it, rebooted it and made a back up. Before i made the backup i put plurr3d back on becasue i thought that the radio files from eclipse were not compatible with the radios on the bionic for some reason. This was all on Thursday. well, this time, it took 3-4 hours for blurr3d to get passed the welcome to andorid please touch the android to continue screen. on the screen it said, "please wait... this may take a few mins" after about 20 mins i got worried so I pulled the battery and rebooted the phone. and got back to the same screen. After i got back to the welcome to android screen, i had to go to football practice and dinner afterwards. when i got home, which was 3-4 hours later, I checked on the phone and it was past that screen and i was able to add my gmail account to it. For some reason or another, the cell and data services were not working. so i left it at that for a day or so and on Friday, I tried using what a lot of people are saying on the Internet which is, RSD lite. you can use RDS lite to flash a stock ROM onto the droid bionic. at that point, i thought that if i got the stock ROM back on, the radios would start working again. well, when I put the phone into fastboot mode it said,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Connect USB
DATA Cable
It also said the same thing when i connected the USB cable to the phone and the computer. RSD lite did not recognize the phone so i tried for a couple hours with the same result. Later on, I read that restarting the computer with the phone in AP Fastboot while the phone was plugged in would get the phone to say,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
This worked, but RSD lite still would not recognize the phone. So then i remembered that i had a stock ROM backup with bootstrap and i did. so i un-installed safestrap (one of the worst mistakes i made so far) and installed bootstrap. so i booted into recovery via bootstrap to restore to stock ROM. things did not go as planned... for some reason or another, it booted up normally. without going to recovery. then it wont to the dual core screen then the bionic eye screen with someone's ROM underneath it (it didn't say someones ROM but it said some one's name then the word ROM) then blurr3d ROM booted up and it kept crashing. so i ended up staying up to around 2-4 AM trying to fix that. i ended up saying forget this and going to sleep.
When i woke up in the morning, i looked at the phone and i had my data and my cell service back so i was confused so i started texting my friends and when i tried to go tot he home screen, nothing happens. but what i learned earlier is that when i reboot the phone, my data and cell service goes away for a couple of hours. So here i am now with my droid bionic, and cant do anything but text and call. i can only call when i get a text from someone, open up the text, and click on the phone number and click call when it brings me to the contact page for the number. I am also not able to access the home screen, the settings folder, or anything besides the notification bar. i really need my phone to use email, games, software (learning how to write java code), and for school in some instances. Any help would be greatly appreciated.
Thank you for your time,
NH85

Seems to me...you lost data along the way.
A possible reason rsdlite is not recognizing your phone might be because you dont have the proper moto drivers installed.
Try this rsdlite and install the correct drivers for your pc...http://dl.dropbox.com/u/63864500/rsd_drivers.zip
Make sure your battery does not die!
Boot into AP fasboot (power and down volume)
Use the cable that came with your phone.
See if rsdlite recognizes the phone.
If it does, you can flash the full 902 xml file (make sure your pc has 4g of RAM tho)
Do you have the full 902 xml file...if not, let me know.

Drivers
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85

i notice that you didn't once mention a wipe data or otherwise cleaning of previous ROM before flashing another (correct me if im wrong). also DO NOT have bootstrap and safestrap installed at the same time, this could be what caused all your problems. in order to switch between the two (which i've had to do for webtop issue), you have to return to STOCK +root, uninstall the currently used strapper, reboot, then install the other. things start getting even hairier if you forget that safestrap has both a safe/non-safe system. you need to be doing the switch on the non-safe system if necessary.
the purpose of safe-strap isn't that it can boot to recovery, it's that it *creates a an isolated ROM installation while preserving your "safe" system in case things like everything your experiencing occur. from what i can tell, you did not change to safe system before flashing new ROMs, again correct me if im wrong. at any rate, a bit of advice for the future is follow directions to the dot, but before even attempting the install read through AT LEAST 3 or 4 pages of user feedback to see what the common issues or install goofs are!
that being said...
having your computer recognize the phone as storage device does not necessarily mean you have the right drivers installed, however it does mean that you probably have the right cable (this is important, bionic is finicky without the proper moto cable). you will know if you have the right drivers if you see in device manager Motorola ADB. when you plug your USB cable in, there should be an option for "PC Mode" which will force the computer to search for the drivers you claim to have installed correctly. if not found, here is your chance to install them properly and test RSD to make sure device is detected.

nh85 said:
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
Click to expand...
Click to collapse
Obviously you don't.
Mass storage and ADB are not the same drivers.
If you are in fastboot mode and your device doesn't connect, it's most likely your missing or don't have the fastboot drivers installed on your computer properly.
Once you get the ADB driver from motorola you can use fastboot start flashing.
The information you need is here
http://forum.xda-developers.com/showthread.php?p=22758211 .

I had trouble using RSD to flash the .902 FXZ.
What I had to do is extract the .img files from the ZIP, and use fastboot through CMD to get everything up and running.
Just open up the XML file inside the zip, it will show you the commands you need to type to flash each section and when to reboot the bootloader

[Q] Help! Fastboot USB but computer isn't seeing my device

Ok so long story short: I installed Cyanogenmod onto my HTC One using their installer, used it for a month or so and decided to flash it back to stock, but not before flashing a Google Play Edition rom (Android Revolution's). The rom got me stuck in a bootloop which i've read should be pretty easy to get out of, however my computer won't recognize my phone. I've also done something while trying to clear caches and what not that says the phone isn't rooted. I've tried to re-root it but since i can't drop the file into my sd file (can't see my phone on my computer) i can't do that either. Whenever i do try to reboot out of bootloader i get stuck at the HTC loading screen. I can get the red FASTBOOT USB and my comp dings when i plug in, but i can't see my phone. I've tried re-downloading drivers. Device manager sees my phone, but i can't access my sd card. I also can't get abd push to work either.
I'm pretty damn new to all this...probably started playing around prematurely. I've read quite a few tutorials so i'm not completely dense as to how all this works, but pretty close to it. If i could just get my computer to see my device, get the root and a new rom file on my sd, i'm pretty sure i could figure the rest out. Also, my apologies if this has been answered before; I did some digging an didn't see anything that helped my issue. Any help would be appreciated.

Also...i should probably mention that i was playing around with the format /system etc commands in CMW recovery...and it's likely i may have rebooted at some point afterwards....so i'm pretty sure that is what is causing the HTC screen issue, but I still feel my main issue here is the inability to get any zip files or anything for that matter onto my sd.
Once again...any help here would be greatly appreciated. Thanks