Database Users

my phone wont boot anymore

Hi,
i used this guide to unroot my g1
everything went fine. untill i got to this step:
4. Start phone in bootloader. [Hold camera+power button]
at the grey screen, it said "not allow" and went back to the screen with the 3 colors. now nothing happens.
boot with home+power doesnt work anymore, same with normal power on (it only displays the Tcom splash screen.
is there anything i can do?

Can you still get into bootloader (camera+power)?

yes,
i've got on my sd card the DREAIMG-RC29 (extractet of course)
but it wont load. i've got some other folders and stuff on the sd card, could this be the problem? i've got no adapter for my PC, so i can't format the sd card.
thx for trying to help me

When you say extracted, what excatly do you mean. You should have the DREAIMG.nbh file in the root of your sdcard (so not inside any folders). Is that the way you have it?

exactly, it is in the root directory

eliah0711 said:
exactly, it is in the root directory
Click to expand...
Click to collapse
Reformat the SD card for FAT32, re-extract that file back to the root directory of the SD and try again. If the same problem exist, re-download the file from here (T-Mobile G1 ONLY!)

ok, i dont really know how, but i was able to access home+power again.
like jamesrdorn said, i reformated the SD card and extractet the DREAIMG to the root directory. I switched it on with camera+power -> still the same error. just for fun i rebooted with phone+menu+power and pressed home during the restart and - tada - it booted into the recovery menu. A friend of mine then told me i should install this mod and it worked.
thanks all of you for your help

Is my HERO REALLY BRICKED!!!???

my phones rooted and I have the Regaw mod ROM load on there, and its been good for a couple days now. Last night I went to sleep and forgot to charge my phone so figured the battery died. I plugged in it for about 10-15mins or so to turn it on and all it does is hang on the HTC bootscreen!!!! then I try to boot into recovery and all I get is at the bottom of the screen it says "Build : RA-HEROC-v1.5.2"!!!! Does this mean my phone is bricked!!!???

Remove the battery. Put it back in. Try to boot.
There are other solutions. As long as it turns on there should be a way to unbrick. Try RUU as well.

i tried the battery pull a couple times im trying the RUU now but what the hell could have bricked my phone over night?

I think what the guy in the 2nd post is trying to say, is that if it is booting, it isn't bricked.
It would be bricked if you couldn't do anything with it, then its like a brick.
I know it is probably a bit scary but ify ou can boot it at all, you most likely can fix it.
Did you make any changes (remove any files?) yesterday at some point, and this would have been the first restart?
I don't know, it could be a number of things.

It is probably not bricked. I bricked my G1 so I have some experience in that area. If you can boot into recovery it is not bricked. When I bricked my G1 I couldn't even get to recovery. let it charge a bit. Th battery is probably just dead. OR. take the battery out and plug it in and try to boot. Let it boot for about 15 mins or so.

no i didnt change anything at all, except my sd card said it was corrupted after unplugging it from my PC improperly. and I didnt reformat it right away. I just tried to RUU and i got an Error 170 a USB connection error

BAttitude7689 said:
no i didnt change anything at all, except my sd card said it was corrupted after unplugging it from my PC improperly. and I didnt reformat it right away. I just tried to RUU and i got an Error 170 a USB connection error
Click to expand...
Click to collapse
Where does the recovery image read from? I know we put it in the root folder of the SD, but does it actually boot from there? Could be your issue...
are you runnings apps2sd or whatever it is called?

yes that possibly could be my issue!! how can i fix my sd card or what should I do?

no I am not running apps to SD

BAttitude7689 said:
yes that possibly could be my issue!! how can i fix my sd card or what should I do?
Click to expand...
Click to collapse
BAttitude7689 said:
no I am not running apps to SD
Click to expand...
Click to collapse
I'm not so sure. I am pretty green when it comes to all this rooting stuff. I'm just trying to help figure it out.
Maybe try booting without the SD card in the phone? Could help to narrow down the issue.
I'm sure someone with more knowledge could help.

yea im booting it now with NO SD and its still hangs at the HTC screen

BAttitude7689 said:
yea im booting it now with NO SD and its still hangs at the HTC screen
Click to expand...
Click to collapse
Can you try plugging it into your USB connection and getting into the ADB shell (in CMD) to see if you can access the phone even though it seems stuck.
I know I did this and was able to monitor the logcat when I thought it was stuck, but it was really just doing a whole bunch of stuff.
Just an idea....again, I'm just fishing here trying to help you out.

it tells me error: device not found
i went to (CMD) then cd C:\android-sdk-windows\tools and then adb devices

you might have to manually rewipe your recovery partition in cmd. I had to do that after the official ruu messed up my phone- it wouldn't boot at all, I had to use the fastboot command: fastboot oem boot, then using my nandroid backup restored my recovery.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

im kinda of a noob at some of this so kinda need to explain it out lol ...I just booted to recovery and pressed *vol up* and got me to Fastboot Mode then it says press <Menu> to reset device, should I do that option?

okay i pressed menu and all that got me was it hanging again at the HTC screen.. should i do all of this with my SD card in or out of the phone?

When you boot it and it gets into the "partial" recovery mode, does the PC see the phone? Can you put RA-Heroc-1.6.2 onthe SD card from there? If so, I'd try flashing the new recovery from ADB...very easy...and see if that gets you a bit further along.
You might also try cheating a bit. See if you can pull a nandroid from the SD card (might have to do this with a card reader), then get Flipz's Kitchen and restore the Nandroid after you boot into recovery.
Just a couple of things I'd try....from experience...
S

okay this is what happens i press vol down and power then is load where the androids are on skateboards and it says press <HOME> for recovery along with a Fastboot mode and Simlock option. I press home and then I see the HTC screen for about 30 secs and then where I normally would see the recovery menu with all the green writing i see all black except at the bottom is says
Build : RA-heroc-v1.5.2

sfox said:
When you boot it and it gets into the "partial" recovery mode, does the PC see the phone? Can you put RA-Heroc-1.6.2 onthe SD card from there? If so, I'd try flashing the new recovery from ADB...very easy...and see if that gets you a bit further along.
You might also try cheating a bit. See if you can pull a nandroid from the SD card (might have to do this with a card reader), then get Flipz's Kitchen and restore the Nandroid after you boot into recovery.
Just a couple of things I'd try....from experience...
S
Click to expand...
Click to collapse
To follow this and break it down a bit more for you:
1. Plug in USB with phone off
2. Turn on phone and get it to the "blank" recovery screen.
3. Run through the flashing of the recovery rom image again (see HERE) but start at step 13 or so.

Try doing the above post..

So... I think I just bricked a G1. You tell me.

Reading the "How to root" thread here. I've rooted a few G1's and a MT3G in the past.
Anyways. I downgraded to RC29, downloaded Amon's recovery and Hard SPL.
Did the whole Telnetd, downloaded telnet from market and mount remount, flash yadda yadda as per stated.
Rebooted and applied the Hard SPL.
After that finished I rebooted and it just hangs on the G1 screen, Home/Power does nothing. Camera/Power does nothing. Trackball/Power just lights the LED up blue.
Will it live the rest of it's life as a door stop?

not being able to boot into anything is a brick but there have been many threads about people who have somehow reversed their brick so just search this forum and see if anything happends who knows it could happen. otherwise its a really shiny paper weight

Bummer. I'll search around a bit more and see if there might be a thread I missed. I don't want to dig into it and do the whole jtag crap since there is still a warranty on the phone.
This is the "How-to" thread I followed and has worked on every G1 I have rooted til this phone which is a brand new one from Tmo.
http://forum.xda-developers.com/showthread.php?t=442480
Searching more I have read about people not flashing a radio before the SPL and caused a brick. If that is true why doesn't it state this as a necessary step?

Flashing the Radio before the SPL is needed for DangerSPL (although I seem to recall a thread debating that - http://forum.xda-developers.com/showthread.php?t=655097 ), I didnt think it was needed for HardSPL, it sounds like a brick unfortunatly, but I am no expert.
It is thought that its safer to flash the SPL and radio ect via fastboot (see link above) , not that it helps to much now, but that is an old guide, it should be updated though

Yep. From what I have gathered is if you can't get into recovery (home+power) or fastboot (camera+power) and it hangs on the G1 boot screen. It's a brick.

-RotorDemon- said:
Yep. From what I have gathered is if you can't get into recovery (home+power) or fastboot (camera+power) and it hangs on the G1 boot screen. It's a brick.
Click to expand...
Click to collapse
its not a brick unless it doesn't turn on at all (depending on how you define the word "brick")
exact same thing happened to one of the G1 replacements my friend got sent to him...we sent it back and they sent him a new one

Nah it's not bricked, the HSpl isn't compatible with your ROM, try flashing he ROM again, or faulty ROM this happens a lot.
Howto fix:
1. Backup any files on your SD card that are valuable to you (you can copy them to your PC's hard drive)
2. Format your SD card to FAT32 ( put your SD in your PC)
Windows: Right-click on SD icon and select format
3. Download the RC29 / RC7 dreaimg.nbh file (don't rename it or your phone won't recognize it):
RC29 (US): http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
RC7(Europe):http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
4. Put the file you just downloaded onto your freshly formatted SD card (make sure it is named DREAIMG.nbh, the rc7 file downloads with .NBH which is wrong)
5. Turn your phone off.
6. Hold down the Camera button, and press the Power button until the bootloader starts.
Note: On some G1s it may require pressing the action button (trackball), while on others it may require pressing the power button.
7. Follow the on-screen instructions to flash the image.
8. When it's done, press the trackball.
9. Press the Call, Menu, and Power buttons at the same time to reboot. You may need to unplug your phone for this to work.
10. And you're done, your phone is in Manufacture default-settings.
If you want to flash a ROM follow a guide (start from the beginning)
Tell me if it worked or didn't worked!
Source: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod

what tally said....
but on the one i described, just to let you know, i flashed the rc29 dreaimg.nbh like 15 times, it would never get off the G1 boot screen

tnpapadakos said:
what tally said....
but on the one i described, just to let you know, i flashed the rc29 dreaimg.nbh like 15 times, it would never get off the G1 boot screen
Click to expand...
Click to collapse
Try flashing the ROM again if you can go to the bootloader(Rainbow) screen try this:
1. take out the SD card
2. download this file ,open the folder and paste the dreaming.NBH file to the root of your SD card(use your pc or another phone to past this on your SD card).
2. you should get a gray screen once the card in placed back into the phone
3. then press power to start update
4. once the update is complete press the track ball then the rainbow(bootloader) screen should come back up,
5. pull out the battery and there you go your phone should work again
Note: If it didn't updated turn of your phone and turn it on by pressing (& holding) Power+Camera button.
Tell me if it worked

Lol, for some reason it double posted my previous post sorry.

He says in the first post Camera / Power dosent load the bootloader

vixsandlee said:
he says in the first post camera / power dosent load the bootloader
Click to expand...
Click to collapse
send it back

vixsandlee said:
He says in the first post Camera / Power dosent load the bootloader
Click to expand...
Click to collapse
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.

tally114 said:
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
Click to expand...
Click to collapse
Interesting, I didnt know that.
Thanks for the info.

tally114 said:
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
Click to expand...
Click to collapse
Doesn't work either. Connected, disconnected, SD card in or out, SIM card in or out and any combination of that.
Logcat just sits and says "Waiting for device" while the phone just hangs on the G1 screen. So unless there is a different way to get into the bootloader besides using Camera+Power I'd like to know.
Camera+Power and Home+Power are unresponsive.

Well... it sounds like you've got yourself a fancy plastic brick, just remember for next time
1. Downgrade
2. Radio
3. Spl
-------------------------------------
Sent via the XDA Tapatalk App

G1 Reverted to RC29 stuck at "Android system recovery utility"

I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?

Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)

There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).

A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.

ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.

I just had this exact experience; have you made any progress, goatlordbob?

same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?

why doesnt there seem to b any help for this matter, smh

bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?

try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html

ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.

Anyone bothered booting using home + power?

shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.

[Q] Almost Bricked MT3G 32b Help Please

Okay so i had rerooted my MT3G after sometime of being left on stock android. I decided to make some adjustments on my device by editing the framework-res.apk. Problem is im running stock android and it just leaves me stuck on the second splash screen after reboot... It doesnt even show the Android screen... Its not bricked as i can go into recovery but i cant reflash the Froyo Ota because of error
Some information about device:
Sapphire PVT 32B Ship s-on G
Hboot-1.33.0013
Radio=2.22.28.25
And when I try to reflash the update it says
Assert failed:!less_than_int(1285103450), getprop("robuild.date.utc"))
E:Error in /sdcard/update.zip
(Status 7)
Everytime I try to reflash it gives me that screen, and i already did a factory reset and wiped cache partition
What should I do??? Note S-On, from official froyo ota, so I think other roms are out of the question.
Please help

Oh and I have access to recovery and fastboot/hboot.

Yay! You get to downgrade and reupdate to 2.2.1. I think I've already got instructions out to do so, give me just a minute to dig them up.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

1. If your using Windows, go to Control Panel->Folder Options->Make sure that "Hide known file extensions" is NOT checked.
2. Go here and download the "sappimg.nbh" and "update1.zip" through "update5.zip".
3. Put all the files on the root of your SD card (this means put them on your SD card but not in a folder).
4. With the phone off, boot into hboot by holding volume down+power.
5. A screen will come up, you'll see a few lines of text, then on the last line you should start seeing a progress bar in the upper right-hand corner. The phone is checking the sappimg file.
6. When the check is done, it'll ask you to hit action to continue (Action is pressing the trackball). Hit the trackball to continue.
7. You'll see a few more progress bars, then the phone will ask you to press "Action" to reboot, do as it says.
8. When you get to the Google activation screen, just turn the phone back off. (Or if you need the phone for SD card access, sign in, to do the next step, then power off)
9. Mount your SD card to the computer and rename "update1.zip" to "update.zip".
10. With the phone turned off, boot into recovery holding home+power until you see a triangle with an exclamation point and a phone. Hit home+power again to bring up the menu.
11. First select "Wipe data/factory reset" and then select "Apply update.zip from SD card".
12. Reboot and let the phone get to the Google activation screen again, then turn it off. (Again, if you need the phone for SD card access, sign in, to do the next step, then power off)
13. Mount your SD card to your computer again, delete the "update.zip" file and rename "update2.zip" to "update.zip".
14. Do steps #10-12 again.
15. Repeat steps #13 and #14 until you've flashed all of the updates, then reboot. Your back to 2.2.1.

That would be great. Thanks a ton.

Thanks a ton. I'll report later to see if it worked or not.

Yea so it doesn't let me get past the 5th step. Its not recognizing the sappimg provided. Its in the root directory so i don't know what the problem is...

Xiaoxion said:
Yea so it doesn't let me get past the 5th step. Its not recognizing the sappimg provided. Its in the root directory so i don't know what the problem is...
Click to expand...
Click to collapse
Try formatting the SD card and putting only the files needed back on. Make sure you backup anything you want to keep.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

Xiaoxion said:
Yea so it doesn't let me get past the 5th step. Its not recognizing the sappimg provided. Its in the root directory so i don't know what the problem is...
Click to expand...
Click to collapse
Yea try reformatting the card and make sure you safety remove USB device after copying the file over.
Sent from my HTC Magic/Dream using XDA Premium App

Nope tried formatting and bought a new sdcard too. Still no go...

Xiaoxion said:
Nope tried formatting and bought a new sdcard too. Still no go...
Click to expand...
Click to collapse
Have you tried using a card reader to transfer the file over?
Sent from my HTC Magic/Dream using XDA Premium App

Yes I formated it to FAT which is the default. And I used a card reader to transfer the file over but it doesn't want to recognize my file. Keeps telling me no file or wrong file type... I used the default card which is SD and a Kensington sdcard as well... Should i format it to a different type?

Format to FAT32.