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

Bricked?

My hero is stuck on the HTC (white screen) reboot, it keeps looping every 15mins or so, until the battery dies.
I tried to go into FastBoot (which keeps flashing, the screen turns on and off), but I can get it to go into fastboot USB if I hold down the "search" button (and the screen stabilizes too)
I flashed the stock rom, but that doesn't help. I even tried to clear all the data by doing, home + back key.
Did I truly brick the phone? I even swapped memory cards to see if it would help, but no luck there.
Any help would be GREATLY apperciated.
Thank you!

I'm still pretty new to the rooting and flashing stuff (I've had my Hero for less than a week) but I ran into the same problem and was able to get out of it. If you have an external card reader that you can use, it would help greatly, because that's how I was able to add data to the SD card without having to access the phone. Turn your phone off and remove the SD card. Plug it into your reader, then into your PC, and add a custom ROM directly to the root of the card (i.e. - NOT inside a folder) like Fresh 2.3.3 or anything else you want to use (I used Fresh because I couldn't get CM6 to load). Put the card back into the phone and boot it into recovery mode (hold the HOME button whole powering it on). You should be able to access the ROM and flash it from there, just be sure to wipe first and backup at some point. Hope this helps!!

Did you completely wipe the phone (data and dalvik) before flashing a new ROM? If you didn't wipe the top 3 options (data, dalvik, ext3) before flashing a ROM, this may be what's causing your bootloop.

Bricking the Hero is very very very hard. Unless you flashed a GSM radio, you're pretty much safe
Go back into recovery, wipe EVERYTHING (except SD), flash original ROM, it should work.
Where is your dalvik cache btw?

cricketman24 said:
My hero is stuck on the HTC (white screen) reboot, it keeps looping every 15mins or so, until the battery dies.
I tried to go into FastBoot (which keeps flashing, the screen turns on and off), but I can get it to go into fastboot USB if I hold down the "search" button (and the screen stabilizes too)
I flashed the stock rom, but that doesn't help. I even tried to clear all the data by doing, home + back key.
Did I truly brick the phone? I even swapped memory cards to see if it would help, but no luck there.
Any help would be GREATLY apperciated.
Thank you!
Click to expand...
Click to collapse
do the stock ruu and you should be
fine...

@jordanjackthomas
I tried to do what you said, I extracted the zip file and placed its contents in the root of the SD card, but when I tried to boot up into recovery mode, It was still stuck on the HTC screen.
@chromiumleaf
I don't think I have, but how would I be able to fix that issue if I didn't?
@derekwilkinson
Luckily, I have a copy of my SD card, So I still have it, if it would be any use?
@Big-O-Devil
I have been flashing the stock RUU for days now, and its still stuck on the same issue, (i just did it now, just to be sure, again) and will leave the phone on, till it dies basically. that way I know that I know I waited for it to boot...

cricketman24 said:
@jordanjackthomas
I tried to do what you said, I extracted the zip file and placed its contents in the root of the SD card, but when I tried to boot up into recovery mode, It was still stuck on the HTC screen.
Click to expand...
Click to collapse
Don't extract the zip file. Just copy it to the root of your SD card. Hold down the home key + the power key to boot into recovery. If that doesn't work, try to using the volume DOWN button + the power key. Then press home when the screen loads up. I'm sure you know this, I'm just making sure you didn't forget anything.

YoungSinema said:
Don't extract the zip file. Just copy it to the root of your SD card. Hold down the home key + the power key to boot into recovery. If that doesn't work, try to using the volume DOWN button + the power key. Then press home when the screen loads up. I'm sure you know this, I'm just making sure you didn't forget anything.
Click to expand...
Click to collapse
Okay before, when I extracted the zip there was a boot.img file in there, but now i'll download
http://link.geekfor.me/freshhero233
and saved that link, and placed that into my SD Card. [will update this as soon as its done]

Great! Keep us posted

cricketman24 said:
Okay before, when I extracted the zip there was a boot.img file in there, but now i'll download
http://link.geekfor.me/freshhero233
and saved that link, and placed that into my SD Card. [will update this as soon as its done]
Click to expand...
Click to collapse
When you connect your phone to your computer does your computer make some kind of connecting. Noise.?.?.
Sent from my HERO200 using XDA App

YoungSinema said:
Great! Keep us posted
Click to expand...
Click to collapse
It's been about 1hr, and its just been on the reboot loop. I don't think it helped :/
Here is the some of the information thats on the "volume down" screen:
(HBOOT SCREEN)
HERC XC SHIP S-ON
HBOOT-1.47
..
Radio 2.42.01.04.27
@Big-O-Devil
And yes it does, I can see the device in ADB list of devices, but it is "offline"...

Big-O-Devil said:
do the stock ruu and you should be
fine...
Click to expand...
Click to collapse
I'm gonna have to agree with Big-O-Devil here, stop trying to do it through recovery and just use the RUU from HTC/Sprint

@derekwilkinson
I have been doing that, I've tried to use the HTC/Sprint RUU and its still the same. I've been flashing the .5 RUU and .6 RUU, but none of which have helped. They are all still stuck in the reboot loop.
Is my hboot version correct?
My device does this when I boot into hboot..
"It also does a SD card check when it boots up onto this screen, says something like
herodiag.zip
etc etc"

cricketman24 said:
@derekwilkinson
I have been doing that, I've tried to use the HTC/Sprint RUU and its still the same. I've been flashing the .5 RUU and .6 RUU, but none of which have helped. They are all still stuck in the reboot loop.
Is my hboot version correct?
My device does this when I boot into hboot..
"It also does a SD card check when it boots up onto this screen, says something like
herodiag.zip
etc etc"
Click to expand...
Click to collapse
Ok so flashing doesn't. Work... look for the stock ruu program that restores your phone back to the its original 2.1.. it's a program that does everything for you... if it works you are going to have to reroot again and start from the beginning.. let me know......
Sent from my HERO200 using XDA App
pm me i will give the file to you.....

Big-O-Devil said:
Ok so flashing doesn't. Work... look for the stock ruu program that restores your phone back to the its original 2.1.. it's a program that does everything for you... if it works you are going to have to reroot again and start from the beginning.. let me know......
Sent from my HERO200 using XDA App
pm me i will give the file to you.....
Click to expand...
Click to collapse
Yes, I too suggest that you re-root.

chromiumleaf said:
Did you completely wipe the phone (data and dalvik) before flashing a new ROM? If you didn't wipe the top 3 options (data, dalvik, ext3) before flashing a ROM, this may be what's causing your bootloop.
Click to expand...
Click to collapse
cricketman24 said:
@chromiumleaf
I don't think I have, but how would I be able to fix that issue if I didn't?
Click to expand...
Click to collapse
From your recovery menu (holding Home then pressing Power to turn the phone on) there is an option called "Wipe". Select that one, then there are 5 options within that. Do the top 3 of them (data, dalvik, ext3). After that, push your Back button which brings you to the main recovery menu. Then select Flash zip from sd card and go through the process of flashing whatever ROM.zip you have on the root of your SD (the whole .zip itself, don't extract all the files out).
If that still doesn't cure your bootloop problems, then you need to download the stock RUU (you can find it at this post: http://forum.xda-developers.com/showpost.php?p=6686401&postcount=2). This RUU is NOT the same as nfinitefx45's STOCK ROM! You have to run this RUU through HTCSync on your PC. But try the wiping that I recommended above first....then do this RUU if that doesn't work. Know that running the RUU will remove your root access, so you will have to re-root again after it's done.

chromiumleaf said:
From your recovery menu (holding Home then pressing Power to turn the phone on) there is an option called "Wipe". Select that one, then there are 5 options within that. Do the top 3 of them (data, dalvik, ext3). After that, push your Back button which brings you to the main recovery menu. Then select Flash zip from sd card and go through the process of flashing whatever ROM.zip you have on the root of your SD (the whole .zip itself, don't extract all the files out).
If that still doesn't cure your bootloop problems, then you need to download the stock RUU (you can find it at this post: http://forum.xda-developers.com/showpost.php?p=6686401&postcount=2). This RUU is NOT the same as nfinitefx45's STOCK ROM! You have to run this RUU through HTCSync on your PC. But try the wiping that I recommended above first....then do this RUU if that doesn't work. Know that running the RUU will remove your root access, so you will have to re-root again after it's done.
Click to expand...
Click to collapse
+1.. that should do the trick for you... good luck....

I apologize, I wasn't using the correct terms.
I don't currently have the phone rooted, I have used the Sprint/HTC RUU_Hero_C_Sprint_2.27.651.5_R_signed_release(2)
file to "reset"(if you want to call it that) back to stock mode...but that doesn't do anything, it still is stuck in a reboot loop.
So currently, I dont have any options other than the default when I press "home" on the phone while turning it on. It just automatically clears the data when I do that.
@Big-O-Devil - I have used that file in that post before, and It doesn't help the situation. It is also stuck in a reboot loop.
@YoungSinema - If the file is different from the STOCK RUU, the "exe" that runs...then I would love to try that out. I went ahead and sent you the pm just incase.

Try running the RUU again via HTC Sync on your PC while your phone is turned on and during the bootlooping.

chromiumleaf said:
Try running the RUU again via HTC Sync on your PC while your phone is turned on and during the bootlooping.
Click to expand...
Click to collapse
How would I do that, since HTC Sync actually never connects to the phone while the phone is turned on and during the boot loop?
How can i run the RUU via HTC Sync?

Can someone help me get back into recovery?

Hi
I have been using Clockwork recovery for months and tonight was flashing ROM/zips as usual, and all of a sudden when I try to get into recovery my Nexus just sits on the colored X. When I pull the battery it reboots fine with the ROM I currently have installed. Then I go back into ROM manager, re-flash clockwork recovery: it says flash was successful, so then I choose to boot into recovery, and again it just sits at the blue, red, green and yellow X.
So then I tried a round-about way by going into ROM manager and choosing to restore a backup. Again, when I choose to restore backup it just boots to the colored X again and freezes there.
I've also tried the regular method of holding power button and trackball and get the same results.
Does anyone know why this might be happening? Right now I'm stuck with a ROM I was just playing with and didn't necessarily want to use permanently....I'm afraid I might be stuck with it forever now
Thanks for any help!!!

I've been searching and I should add that my bootloader is not unlocked

Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.

Jack_R1 said:
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Click to expand...
Click to collapse
Well I ended up wiping all user data in fastboot and now I get nothing but an X nomatter what I do, won't boot at all.
All I can do is hold down the power button and trackball and get the page that says
bootloader
reboot
reboot bootloader
power down
the only way I'm going to get this fixed is to use my computer and I've never done it that way...I've always used ROM manager
I'll read the links but I think I'm screwed because a lot of this is over my head
Thanks for the links !

1) Try to follow "Unroot/restore" guide first, see if you can restore functionality using PASSIMG method. Once you have functional FRG33 with recovery, you can root it, replace the recovery and install custom ROM of your choice / update to FRG83G.
2) If nothing helps - consider a) replacing your phone, b) unlocking the bootloader and flashing recovery through fastboot.
Getting in over your head is sometimes a good way to expand your horizons

Hi Jack
Thanks for the help
I'll do some reading and see what I can do....got two feet of snow here so I guess I have the time
worst comes to worst I'm still under warranty.

Well I tried the instructions but nothing happens..it just sits on the screen with the androids skateboarding. I renamed the zip and moved it to my SD card but it doesn't seem to even search for it, let alone find it. Really wish I had not deleted storage. At least I had a working ROM at that point.

Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?

Jack_R1 said:
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Click to expand...
Click to collapse
Hey Jack...
Sorry for taking so long to respond...I finally had to crash for awhile, my brain was frying.
Yes I did what you describe: downloaded FRG33, renamed it PASSIMG.ZIP(not ZIP.ZIP) moved it to SD card just like any ROM and held down volume and power button and came to the screen with the three androids. Then it just stayed there, nothing happened.
The only thing is I had to use my backup Nexus One(EDGE only on ATT model) to move it to the SD card as I don't know how to access the SD card with the device acting like this. If I connect the device to my computer while the three androids are on the screen, I hear it connect to the computer, but nothing pops up allowing me to access the SD card....
Like I said I'm a noob at this I appreciate you trying to help me here

About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.

Rusty! said:
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Click to expand...
Click to collapse
Hi Rusty
Sorry I somehow missed your post here. Yes I see some text flash up...takes a little longer than 3 seconds...maybe 8 seconds...
At first it says I'm in Fastboot, but then I press the power button and then it says HBOOT at the top.....that's when the text flashes on the screen. It flashes too fast for me to read it though....but nothing happens after the text flashes on the screen.

I'll be damned guys....I got it working! After responding to Rusty's post above, I decided to give the whole thing another try. Well I went thru the whole process of putting the file on the SD card and realized I had in fact renamed it zip.zip....it LOOKED like it was only ZIP, but when I clicked on the file while it was still on my PC, it said it was zip.zip...that's when I knew what the problem was.
My problem now is getting it re-rooted. Originally I used the Universal Androot application..the true one-click method...I just tried it again and it didn't work.
Is there a way to downgrade to a version where this app will work again?
Thanks guys you really helped me out here!!

Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.

Jack_R1 said:
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Click to expand...
Click to collapse
Yup I'm already rooted!!! Thanks man!!!! Took 12 minutes!!

Okay I'm having another issue: SuperOneClick said I was rooted,I have the superuser icon in my app drawer, but ROM manager will not flash Clockwork mod recovery and Titanium Backup says I do not have root rights??

well I rebooted and now have root rights but am still getting an error when I try and flash clockwork mod: it says: "an error occurred while flashing your recovery"

Do you have Busybox installed?

Jack_R1 said:
Do you have Busybox installed?
Click to expand...
Click to collapse
You're going to think I'm a dip**** but I don't even know what busybox is?

Let's just say it's an app that the system needs Go to Market, download and install it, try again. If it doesn't work - you can try to install custom recovery manually, using another guide from Wiki. Look in "Installing Recovery" for "For locked bootloader - flash_image using Terminal" guide. If you don't know what Terminal is - download "Android Terminal" by Jack Palevich from the Market.

Use the fix problems button in Titanium Backup to install it, long story short is it lets you use a bunch of native Linux commands that as missing from Android.

[Q] Soft-Bricked G1

So I purchased a used G1 and I knew it has some software issues. I have no idea what version OS or anything is on this phone. Issue is it will not boot up into the OS. After researching (I am new to android) I have found what it can and what I cant get it to do. I can get into recovery mode no problem and after an ALT-L I see "Android System Recovery <2e>". The phone usually boots into this mode straight away, or I can hold home+power and it will enter the mode. Tried doing a "wipe data/factory reset" but nothing changes. If I reboot the phone and hold "back" I would expect it to enter Fastboot mode where I could do stuff. Instead I see the "rainbow screen" very briefly and then a message saying that if I want to restore factory setttings press send, otherwise hit any other key to cancel. No matter what I press nothing happens and I have to pull battery. I can only get into this mode every now and then. It seems pretty finicky about getting into it, and again no options when I do. Finally the camera+power to get into the bootloader does nothing. I can get the PC to see the phone when in recovery mode. It showed up as a mass storage device and i got that changed over to "Android Phone" by installing the SDK drivers.
Is there anything I can do on the recovery screen? That is the only thing that consistently works. I have tried a few update.zip files (various OTA updates I downloaded) but I either get a "No signature" error or it starts installing and then immediately get an "Installation aborted".
Any help to get this up and running would be appreciated. Hopefully its not just useless. For now an OEM 1.5 build is really all a i need. I can worry about updating/rooting later.

Download dream.nbh and format your sd card then place the dream onto ur sd card reboot holding home+cam button and let it do its magic that's how I fixed mine I'm sure if you go to the htc site you will find all the files u need just do a bit more research before trying this
Sent from my HTC Magic/Dream using XDA App

I mentioned in my original post that the camera+power button to enter bootloader mode does not do anything. I have already researched solutions, but it only seems I have access to the recovery mode screen. What can be done from there to assist with this issue (if anything)?

Download and flash the files from here http://developer.htc.com/adp.html (ota radio and system image) rename them update and flash them one at a time
Sent from my HTC Magic/Dream using XDA App

As for the no sig error just do some reasarch on adb shell and flash clockworkmod recovery from there its easy once u do some searching.....dw a couple of weeks ago I was you lol it'll pan out ok the people round here are really helpful
Sent from my HTC Magic/Dream using XDA App

Does this require adb? I have not been successful in making my pc get an adb connection. When in recovery mode the phones shows up on my pc and I got it to show up as android, but "adb devices" does not show anything listed. Everything referencing adb says it needs USB Debugging enabled, but I cant do that I cant get into the OS to enable. I dont seem to be able to enter fastboot mode either (see original post).

Download the radio and recovery image format sd card rename the ota radio update.zip boot into recovery and select apply update from sd card one you have that done delete the update.zip and then place the recovery image on sd card but rename update.zip and do the same....should work for ya
Sent from my HTC Magic/Dream using XDA App

When trying to update the radio files (tried all 3 versions on the download page) I get the "E: No signature (5 files)" error. Can I generate a valid signature for the files?

its worth a try lol if that dont work then i really dont know whats wrong lol

So far I have tried the following files:
The following pass verification and I get to the "Installing update..." but I then instantly get an "Installation Aborted". No other error message as to why:
signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip
signed-kila-DRC83-from-CRC1.c41b93c1.zip
signed-kila-ota-148830.de6a94ca.zip
signed-PLAT-RC33-from-RC30.zip
signed-RC30-from-RC29-fat.1582cace.zip
The following I get a "No Signature" error:
signed-dream_gfh-ota-147201.6d1386de.zip
ota-radio-2_22_19_26I.zip
ota-radio-1_22_12_29.zip
ota-radio-1_22_14_11.zip
I did a Wipe data and Cache before each update.zip attempt and this was using the "Android system recovery <2e>" screen.
Ideas? I will look and see if I can add a signature to the radio files.

dont spose u flashed the recovery with clockworkmod recovery 2.5.0.7
too short

I have not been successful flashing anything to the phone so far. All this was done via the "Android system recovery <2e>".
I signed the radio files myself, but they came out identical and same issues occurred. No idea what the "No signature" error is. Seems like a bunch of people get it on the forums, but no solutions. No idea why the good updates suddenly abort.

forum.xda-developers.com/showpost.php?p=4647751&postcount=1

Unfortunatly that seems to require fastboot, adp, or a rooted phone. I tried installing another SPL and I keep getting the "No Signature" error.

wow man your having a tough ass time lol ill keep researching for ya

i think your home button maybe stuck lol
far to short

You know thats not a bad idea. It does actually boot into recovery mode without holding the home button like you are meant to. Would holding home when powering on prevent the boot loader from starting if I hold the camera button?

on my g1 if i hold home power and cam buttons i get the bootloader/fastboot menu

So I ordered a new battery for it today too. The phone does not seem to work too long without being plugged in. Maybe that will help.
I also managed to capture some pictures of the screens I have, so maybe that will assist people with diagnosing the issue.
The first is the rainbow screen I get when holding back on a reboot. It flashes for 1 second or so and then displays the white screen with blue text. The last pic is the recovery menu I have access to.
It looks like this is a fully stock phone, no flashes. I am going to keep trying to get into that bootloader screen. Getting into the rainbow screen works once every 20 tries or so. Maybe the bootloader is similar. Hitting send on the white screen does nothing and requires a battery pull to reset phone.

how long can you stay in the coloured menu for ?????? also what happens if you stay there like what options do you get???

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