Database Develop

Freeze at G1 Splash SCreen, I Need Help!!

Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped

tehseano said:
Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped
Click to expand...
Click to collapse
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.

andonnguyen said:
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.
Click to expand...
Click to collapse
Sorry, I should have provided more information, and explained that the 2nd half of this post was my original post, which was just me asking how to correctly use ADB. I do already have JF 1.41, I upgraded yesterday. It wasn't my first theme I installed either. I was using Vintage War (for the Dream), but it hadn't been updated for 1.41, so I was trying the standalone apk adb push method found in this forum, which is where this post first oriented.
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
But like I said this wasn't my first time trying to mod the phone, I've had it rooted for a month or so now, and have been keeping up-to-date.
Any more information I can provide, please let me know. My phone is my livelyhood, I need it. So if anyone can help, the sooner would be better. Either way I am entirely greatful for any help anyone can provide. Thanks in advance!

tehseano said:
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
Click to expand...
Click to collapse
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)

andonnguyen said:
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)
Click to expand...
Click to collapse
....How do I get out of the loop. My phone doesn't get passed it. There has to be something I can do in console or recovery or something. I'm really sorry if I'm coming off as rude or demanding but I really need a phone, and I need it right now. I don't know what more I can tell you before someone can finally give me a solution (sorry)

1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.

Datruesurfer said:
1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.
Click to expand...
Click to collapse
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it. Regardless thank you so very much, you are my Savior right now!

tehseano said:
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it.
Click to expand...
Click to collapse
That's easy. Just grab a copy of the fastboot utility and the images off your sdcard in the 'nandroid' directory and boot your phone into the SPL. Plug your phone in via usb and press the back button once and you should see "Serial0" change to "FASTBOOT" Then open up a windows command prompt in the location of the exe you downloaded and run:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
fastboot reboot
Your phone will come back up with all of your applications, settings etc from when you did the backup. Keep in mind you need the HardSPL to do this though(look for three androids on skateboards in SPL). The G1 factory bootloader does not support fastboot, only NBH images that come from the factory.

Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.

Isn't the 4 color screen the standard bootloader that ships with retail G1's (not a dev phone bootloader)?

lugiamx said:
Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.
Click to expand...
Click to collapse
I had the same problem, almost verbatim. ADP1.1, JFv1.41, ran the Holiday update 1 of 2, no problems, did the 2 of 2 update, got stuck at the flashing Android boot screen. Pulled the battery, rebooted, same thing, waited 2-3 minutes at the flashing screen and was just about to pull the battery again and then all of a sudden the damn thing came to life, the OS loaded up and now everything's working fine. Gave me quite a scare.

ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.

chinoman said:
ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.
Click to expand...
Click to collapse
Why have you just hijacked a 5 month old thread? You haven't given use any details either. Fastboot is available for all OS's, it will work on your computer, you just probably don't know how to use it. Please make a new thread in the Q&A section where we can help you out there.

This should be closed or moved to Q&A.

hey man just unroot ur phone and root it again u soft bricked ur phone its ok

hey just try to unroot k

hey if u want me to fix it for u just email me at [email protected] and ill help u

[Q] N1 in trouble! Please help

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!

[GUIDE] [01/05/2011] Root your Incredible (AMOLED & SLCD Support!) + FAQ

Updated 01/05/2011
Support for both AMOLED & SLCD owners!
With the release of Unrevoked 3.31, DINC owners are now able to obtain root and S-OFF with the Nov OTA and it also supports recoveries for both AMOLED and SLCD users!
I have put together an extensive guide on how to get root for both AMOLED & SLCD users! Rooting is now even easier than ever.
The guide is available at http://jonsuh.com/2010/11/root-your-droid-incredible-how-to/
FAQ
Blank Recovery Screen Issue
For those of you coming across the issue of the blank/black recovery screen:
Do NOT boot straight into recovery with Volume Up+Power.
Boot into HBOOT FIRST with Volume Down+Power.
Then select RECOVERY from the HBOOT menu.
I rooted before the OTA and the OTA will not install
Read my article on how to Unroot your Droid Incredible at http://jonsuh.com/2011/01/unroot-your-droid-incredible/
Then read my article on how to root.

link doesnt work

I apologize; link is fixed and should be working now.

Looking to try this, but my SD card appears to be formatted to FAT16. How do I format it to FAT32?
Edit: Spoke too soon, got it. I'll post an update when once I'm done.

works perfectly took about 45 minutes
Sent from my ADR6300 using XDA App

papi92 said:
works perfectly took about 45 minutes
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It is more time consuming but it does work! Glad to know u were able to get it to work. I think it was worth it. So much better having root back
Sent from my ADR6300 using XDA App

I'm already S-Off and rooted, running (mostly) stock. I skipped to step 5B, to update to the OTA update. However, when I attempt to apply update.zip, it fails during the "Verifying current system" step. The text is below:
assert failed: apply.patch.check("/system/app/Mail.apk", <insert two long non-matching hash values here>)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Anyone run into this or have a clue?
Thanks.

danman7 said:
I'm already S-Off and rooted, running (mostly) stock. I skipped to step 5B, to update to the OTA update. However, when I attempt to apply update.zip, it fails during the "Verifying current system" step. The text is below:
assert failed: apply.patch.check("/system/app/Mail.apk", <insert two long non-matching hash values here>)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Anyone run into this or have a clue?
Thanks.
Click to expand...
Click to collapse
Well truthfully, the OTA update doesn't do much but add more crapware. There isn't any other reports of the OTA being a significant update so you'd be safe to not even install the OTA. If you're annoyed with the reminder, if you've done all I've told you to, if you click "Install" it should just time out and not do anything and never remind you again.

Not Working For Me
This process does not appear to be working for me.
After doing all up to and including the "ADB" stuff and typing "reboot bootloader", my phone just boots to the bootloader and does nothing. I never get the prompt to process the update.
Where did I go wrong? I've tried this four times with the same results.

ozone777 said:
This process does not appear to be working for me.
After doing all up to and including the "ADB" stuff and typing "reboot bootloader", my phone just boots to the bootloader and does nothing. I never get the prompt to process the update.
Where did I go wrong? I've tried this four times with the same results.
Click to expand...
Click to collapse
Did you make sure you didn't rename the file something different? It should be "PB31IMG.zip" in the root of your SDCARD.
Also did you make sure your SDCARD was formatted to FAT32? and not FAT/FAT16?

UNREVOKED 3.22 HAS BEEN RELEASED.
Get your copy at www.unrevoked.com.
This thread will be changed within the next 24 hours to accommodate the new Unrevoked. No longer need to downgrade to root.

jsuh said:
Did you make sure you didn't rename the file something different? It should be "PB31IMG.zip" in the root of your SDCARD.
Also did you make sure your SDCARD was formatted to FAT32? and not FAT/FAT16?
Click to expand...
Click to collapse
No good.
I am running Windows 7 64-bit.
I formatted the removable sdcard to fat32 and the PB31IMG.zip file is named correctly.
I type in "./flash_image misc /sdcard/mtd0.img" and immediately get the "#" prompt after it confirms my entry.
I then type "reboot bootloader" and the phone goes to the bootloader and just sits there until I tell it to reboot.
Should I be doing all of this from the internal storage instead of the removable card?
New Info:
I just tried it again and this time instead of rebooting from the bootloader screen I selected "bootloader" and it checked the image and gave me the option to flash. I said "yes" and it is now loading the image.

ozone777 said:
No good.
I am running Windows 7 64-bit.
I formatted the removable sdcard to fat32 and the PB31IMG.zip file is named correctly.
I type in "./flash_image misc /sdcard/mtd0.img" and immediately get the "#" prompt after it confirms my entry.
I then type "reboot bootloader" and the phone goes to the bootloader and just sits there until I tell it to reboot.
Should I be doing all of this from the internal storage instead of the removable card?
Click to expand...
Click to collapse
Nope, you shouldn't, but no worries, the new Unrevoked version should be able to get you root without having to follow all my directions.
Just go to www.unrevoked.com/recovery then download and run the proper version.

Uh-Oh!
I think I just bricked the phone.
After saying yes to flashing the image, the phone went black and never woke up. now I can't turn it on although the soft buttons light up when I press the power button.
Is there any key combination that will get me to recovery or am I screwed?

Updated 12/2/2010
With the release of Unrevoked 3.22, I provided instructions for root for BOTH AMOLED & SLCD owners!
Enjoy
http://jonsuh.com/2010/11/root-your-droid-incredible-how-to

ozone777 said:
I think I just bricked the phone.
After saying yes to flashing the image, the phone went black and never woke up. now I can't turn it on although the soft buttons light up when I press the power button.
Is there any key combination that will get me to recovery or am I screwed?
Click to expand...
Click to collapse
Is there any way to get the phone back?

ozone777 said:
Is there any way to get the phone back?
Click to expand...
Click to collapse
You can try to hold volume down and the power button to get back into hboot. That may get you back to a workable position.
Hope that help...

g00gl3 said:
You can try to hold volume down and the power button to get back into hboot. That may get you back to a workable position.
Hope that help...
Click to expand...
Click to collapse
Already tried all the standard key combos with no success.
I thinks its time to stick a fork in it.
Time of death...3PM.
This doesn't mean I won't try again with the replacement Verizon sends out to me.
Gotta get back on the horse.

ozone777 said:
Already tried all the standard key combos with no success.
I thinks its time to stick a fork in it.
Time of death...3PM.
This doesn't mean I won't try again with the replacement Verizon sends out to me.
Gotta get back on the horse.
Click to expand...
Click to collapse
Pull the battery out put it back in and turn it back on (u said that it was an slcd?). U mentioned that the soft keys turn on right? Have u tried re running unrevoked with the new recovery mod for slcds? Look at my site for directions.
It may b that unrevoked would still recognize ur phone being plugged in and rerun the root process with the proper recovery.
Sent from my ADR6300 using XDA App

The 3.22 works great. The one thing I kept getting hung up on was after I installed the drivers by going into device manager etc etc was that windows was still asking me to install hardward drivers for usb device... so I followed along with windows and installed the driver again. Immediately after I installed the drivers for the second time unrevoked picked up my phone and started the process. It went all the way through and went to "done." (forgot to remove the PB31IMG.zip from trying to push the downgrade before - so it tried loading the update and failed...all I had to do was choose dont reboot, that brought me back to the hboot screen then unrevoked picked it back up).
The one problem I kept running into was that the new 3.22 unrevoked wouldnt pick my phone up even after I installed the drivers with device manager etc. So I tried a few different computers...still nothing and still asking me a second time to install the drivers. After I installed the drivers the second time everything was smooth from there.

[Q] No functional recovery image... now what.

Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.

A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!

Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.

Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me

Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120

Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?

Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery

Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).

zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D

are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!

Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.

I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.

Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?

Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.

For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.

Can someone help me? I am so lost

I've been having trouble with my Vibrant and with T-Mobile in limbo I picked up a N1 off ebay to hold me over. This thing is driving me insane!
The phone came with CM7 installed on it, but the person that shipped it to me didn't erase any of there stuff so I figured I would flash a fresh image on the phone to take care of things. I've flashed my Vibrant a dozen or so times and never had an issue. Flashed the N1 and it comes up with an X made of 4 different colored lines and a little lock at the bottom. I know some roms take a while to load so I let it sit for an hour. Nothing.
Since I've been trying everything I can find out how to recover the phone including all of the guides on the wiki. I'm at my wits end at this point. I can't get into clockwork at all on the phone. It gets stuck in the bootloader and if I select recovery it just takes me back.
I've got droid explorer running, and the phone shows up, but it doesn't show anything on the phone, no folders or files and won't let me load anything on to it. (it says it is, but then stays blank) I have no clue what to do at this point short of taking a sledge hammer to it. (obviously I'm posting this as I consider that to be plan B)
I don't need anything special, I just want a working phone. Is that really so much to ask for?

If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?

Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?

danger-rat said:
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
Click to expand...
Click to collapse
I'm sure I haven't, just what I found in the wiki
I tried the PASSIMG.ZIP and it failed
I tried Amon_Ra's Recovery and the only way I can get it to do anything is to tell it to flash in droid explorer and it just reboots and gets stuck. Now nothing is showing up file wise in droid explorer and I can't transfer the image onto the root.
When I could get into clockwork I tried flashing different roms but it would just go to a screen with the clockwork logo and get stuck.

amolji said:
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Click to expand...
Click to collapse
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?

n25philly said:
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
Click to expand...
Click to collapse
in the bootloader I think (dont take my rookie rooting words too serious) theres a hard reset menu under recovery. it will take you to another x and press volume up and power for the menu to pop up.

try fastboot a recovery image (either Amon Ra or CWM) and see if you can get back to recovery after that.

Well I'm assuming you already have a custom recovery since it came with CM and you've, as you said, flashed it (what exactly do you mean by that by the way? flashed another rom?). So all I can recommend is that you wipe a few times and try flashing a few different roms and hopefully one will boot. Not the best advice in the world but its always worked for me before and my N1 and my DEXT before hand when I've messed them up!

You still did not say what you flashed to your phone.
Anyways follow the restore to stock guide.
I don't know what this Droid manager thing is but don't use it. Install the sdk.....