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.
Related
Hi,
Forgive my noobishness but it's late and I hate doing this lol.
So I rooted my phone way back when it was just JF. When I turn on my phone with Home and Power I get a screen with yellow text and a white and black background. I assume this is the bootloader?
Anyway I recently showed my friend over msn the new guide on rooting. Went fine. Today I tell him about Ion. So he updates his radio, then the SPL and now when he turns it on it keeps booting to a screen with a phone and a ! in a triangle. Alt L shows commands etc. So it keeps booting to this screen. Fair enough we need to now update with Ion. However he doesn't have a SD card reader so I have no idea how to get the update on his card.
I'm thinking adb but I don't know how to go around setting that up seeing as his phone wont boot.
Anybody care to help me out? Thanks for your time.
The screen you are seeing with the yellow text is not the bootloader, its the recovery utility.
Camera+power gets to the bootloader
Home+power gets to the recovery
You can put the update.zip on your card and then put it in his phone to flash it that way.
Check out this page for adb help :http://forum.xda-developers.com/showthread.php?p=3820215
After installing the new SPL. you have to install the rom. So basical;y, if he wants ion. just rename it as update.zip, place it in the SD, turn off the phone, hold Home+power, goes into the recovery console, do a Alt+W, then Alt+s.
First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help
Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)
ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.
please help is desperatly needed.
i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle
waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.
I tried and stuck in the exactly same problem as [robotician]. I have MT3G.
robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.
@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.
So, after following this forum on and off over the past few months, I finally decided to root my Rogers Dream.
I was one of the first customers to receive a phone with SPL 1.33.0010, as mine was shipped to me directly from rogers as a hardware upgrade. Because of this, rooting was a little more difficult for me than I had initially anticipated, however, after having found this thread (http://forum.xda-developers.com/showthread.php?t=558301), I was able to downgrade to SPL 1.33.2005.
From this point, I started following the instructions found here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod. I was able to re-flash the downgraded OS, and rebooted to a T-mobile G1 splash screen. After going through the various steps, I got stuck where it said to reboot into recovery mode. I held down the home key while powering up, as instructed, but instead of booting to the recovery screen, I was greeted with an image of an exclamation point inside a triangle, hovering over a cartoon of a G1.
I was able to reboot using the 3 fingered salute (send-menu-power), but I was unable to load the recovery screen. I then attempted to bring up the boot loader by holding down the camera button while powering on. The screen I was greeted with did not resemble the boot loader I was used to seeing. It is composed of four horizontal coloured bars, and lists the phone information as follows:
DREA210 PVT 32B
HBOOT-0.95.000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I'm looking for suggestions on how I should proceed from here. Any help would be most appreciated. Although the phone does make phone calls, and will send and receive text messages, it will not send or receive data, unless connected to wifi.
Thanks,
Grant
So I'm a little rusty but let me give it a shot. While holding home + power it may seem to just get stuck after a minute, but have you tried pressing alt + L ? This makes the recovery text visable (if it's not by default).
hope this helps..
Looks like you've ended up on the stock g1 bootloader.. did you flash the rc29 DREAIMG?
goldenarmZ said:
Looks like you've ended up on the stock g1 bootloader.. did you flash the rc29 DREAIMG?
Click to expand...
Click to collapse
Yes. The phone thinks it's a T-mobile G1, but it still works with my Rogers SIM.
sonikamd said:
So I'm a little rusty but let me give it a shot. While holding home + power it may seem to just get stuck after a minute, but have you tried pressing alt + L ? This makes the recovery text visable (if it's not by default).
hope this helps..
Click to expand...
Click to collapse
I did this, and the recovery text did indeed become visible, however, I now have a new problem.
I hit Alt+W as per the instructions in the wiki, and it reset the phone. I then hit Alt+A, and nothing happens.
This is the text I see on the screen when I'm in recovery mode:
Androind system recovery utility
E:Can't open /cache/recovery/com
mand
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
After attempting Alt+A, I hit Alt+S, just to see what would happen. Of course, it tried to update from package, but returned an error because there is no "update.zip" on the phone. I'm tempted to rename "update-cm-4.2.5-signed.zip" as "update.zip", just to see what happens. I'll post again once I've done this, but any suggestions from more experienced people would be most appreciated.
Grant
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Alright, so I renamed "update-cm-4.2.5-signed.zip" as "update.zip", and it aborted the installation because there was no signature. I did the same thing with "signed-dream_devphone_userdebug-ota-14721.zip", with the same result.
It sounds like you still have the stock recovery image
jackslim said:
It sounds like you still have the stock recovery image
Click to expand...
Click to collapse
When you say stock recovery image, are you referring to the one I have installed on the phone already, or the one I'm trying to install with no success?
The image currently on the phone is the DREAIMG.nbh (rc29), which I downloaded via the wiki. The images I am trying to load also came from links in the wiki.
By recovery I'm refering to what you access when you boot with home + power where you can apply your updates (where you're seeing your triangle & exclamation point)
I just looked at cyanogen's wiki and it seems like that particular part could stand to be updated androidandme has a decent guide on how you could do this though.
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
I'm not sure if flashrec works with RC29 which is what version you should be on after flashing DREAIMG.nbh, but you can give parts A1, A2, & A3 a shot, that would probably be the easiest way to update your recovery. If you can't get flashrec to work skip down to B2 and that will show you how to do it using telnet which does work from RC29
Once you update you're recovery image you should be able to apply "update.zip" or without renaming them by selecting the "apply any zip from sd" option
Thanks, Jackslim. I did as you suggested, and was able to install the CM update, as per the wiki, however, when it boots up, it shows the blue cyanogen android, and then reverts to a completely blank screen. I'm going to try reinstalling everything to see if that fixes it. Thanks for your help though.
gmupps said:
Thanks, Jackslim. I did as you suggested, and was able to install the CM update, as per the wiki, however, when it boots up, it shows the blue cyanogen android, and then reverts to a completely blank screen. I'm going to try reinstalling everything to see if that fixes it. Thanks for your help though.
Click to expand...
Click to collapse
After you install that recovery image you still have to go through the steps to install the ADP image before you add the cyangen update, then you should be cookin' with crisco
So just start back up on cyanogen's wiki from the section called "File Download"
Just to clarify, even though it is not booting up properly, I am now able to install whatever I want using recovery mode, so it's just a matter of figuring out what will work. Thanks again for all your help.
jackslim said:
After you install that recovery image you still have to go through the steps to install the ADP image before you add the cyangen update, then you should be cookin' with crisco
So just start back up on cyanogen's wiki from the section called "File Download"
Click to expand...
Click to collapse
I did get it working, thanks. Now I just have to reload all my contacts and apps, but I have already noticed a difference in device responsiveness. It's like going from Windows Vista to Windows 7. Thanks again.
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..
hi, my phone has stuck on the "google" icon when i start it. I have tried the "bootmode" you know when you hold volume and on/off button. There i tried to push on "reboot", "recovery", nothing is happening same thing. The only thing i have managed so far is installing driver usb for android phone in my computer, but i cant find the phonefolder in "My computer" to put reboot/update files to make the phone work.
How can i make the phone work? please help me im not so good at this.
please someone???
distortedloop said:
Everything you need should be in these two threads:
http://forum.xda-developers.com/showthread.php?t=878786
http://forum.xda-developers.com/showthread.php?t=895545
The second one has pictures and is very easy to follow.
Click to expand...
Click to collapse
Try this, thanks go to DistortedLoop
Check the links kenvan posted above.
You don't want to see the phone mounted as USB, you need to see it with the fastboot command from your DOS or unix terminal.
Then push ClockWork recovery to the phone.
From CW recovery you should be able to use it's tools to get you running again, or at least adb should work so you can mount storage and push files to it via adb.
I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
somii87 said:
hi, my phone has stuck on the "google" icon when i start it. I have tried the "bootmode" you know when you hold volume and on/off button. There i tried to push on "reboot", "recovery", nothing is happening same thing. The only thing i have managed so far is installing driver usb for android phone in my computer, but i cant find the phonefolder in "My computer" to put reboot/update files to make the phone work.
How can i make the phone work? please help me im not so good at this.
Click to expand...
Click to collapse
i have tryed this one : http://forum.xda-developers.com/showthread.php?t=895545
once i get to the phase where i select recovery in bootloader it just goes to the screen with the google logo and the unlocked padlock icon and it sticks there, any suggestions? i have tried to entering the recovery command again in the command prompt, still same problem =(
dinan said:
I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
Click to expand...
Click to collapse
nothing the phone started to hang/freeze and then vibrating for about 40 seconds, i took out the battery the it was stucked in on the google icon.
dinan said:
I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
Click to expand...
Click to collapse
kenvan19 said:
Try this, thanks go to DistortedLoop
Click to expand...
Click to collapse
i have tryed this one : http://forum.xda-developers.com/showthread.php?t=895545
once i get to the phase where i select recovery in bootloader it just goes to the screen with the google logo and the unlocked padlock icon and it sticks there, any suggestions? i have tried to entering the recovery command again in the command prompt, still same problem =(
Ok since you say you have a padlock on the boot screen, I assume you know how you unlocked the bootloader.
Turn the phone on into fastboot (hold power and volume up), then connect the phone to the computer via USB. Flash clockwork recovery (3.0.0.5 preferred) and then you should be able to enter clockwork recovery assuming you did it correctly. Push this rom (http://forum.xda-developers.com/showthread.php?t=884093) to your card and flash it in recovery.
dinan said:
Ok since you say you have a padlock on the boot screen, I assume you know how you unlocked the bootloader.
Turn the phone on into fastboot (hold power and volume up), then connect the phone to the computer via USB. Flash clockwork recovery (3.0.0.5 preferred) and then you should be able to enter clockwork recovery assuming you did it correctly. Push this rom (http://forum.xda-developers.com/showthread.php?t=884093) to your card and flash it in recovery.
Click to expand...
Click to collapse
Yes i know, can you be more specific`? step by step? im noob sorry for bothering you., how do i push to my card?
I have fixed my phone, my phone was liquid damaged. So i putted the hole mainboard in 100% alcohol and after 20 min i took it out and let it dry. And then it worked fine!
It just happened to me an hour ago. I tried for a few time to remove the battery and start it up (even with a new one). I also thought it might happen since the battery was drained so i let it recharge for a while with no success.
Eventually i attached the device to the computer's usb, waited and started it. and it worked.
Don't know if that was what solving it - but it back working.