G1 not going into recovery, help! - G1 Q&A, Help & Troubleshooting

I had my phone rooted and working fine on CM5 but I had the CM/JF recovery.
I wanted to update to a new recovery so I downloaded Clockworkmod's ROM Manager. I flashed the recovery and rebooted into recovery. The phone will hang on the G1 screen if I try to go into recovery, but if I let it boot normally it will go into android.
How can I fix this?

If you have a SPL that allows FASTBOOT, you can FASTBOOT, connect to the PC, and flash the recovery image from there.

Everthing I read about fastboot is done over linux, is there a way to get it running in Windows?

Has nothing to do with linux. Is multiplatform.
http://forum.xda-developers.com/showthread.php?t=532719

Windows 7 is being a pain in the ass and not letting me install the USB drivers. I don't know what to do

Use google.
It has been asked already. I had Windows 7, and it worked.

The only thing I find is how to get the Hero to sync with W7. Should i follow those steps anyway?

I cant post links but I used a method on theunlockr
And Winblows 7 is still telling me it is unable to install my device.
.....

It is the same.

just go to amon ra's thread on his 1.7.0 version and there is instructions on how to flash his recovery from terminal on the phone its really simple that way

In his thread it says not to flash it from within CM5 :\
That's probably what happened in the first place, i flashed a recovery from within CM5 and this caused my problem.
EDIT: Tried it anyway and it didn't work.
EDIT EDIT: After messing with the HTC sync drivers I was able to install them and my computer reads my phone when I do 'fastboot devices'. However I have to go to school so I will have to flash the recovery after work. I hope this works

I was able to successfully flash the recovery with Fastboot. Thanks for the help

Related

How to wipe w/o recovery or adb?

I was following the steps to update to Cyanogen's newest ROM and going through the steps on Cyanogenmod. I wiped, had both ROM's on my SD card and fell asleep while it was flashing the HTC recovery image. Well I must not have slept long and for some reason I thought it was done, but apparently I rebooted before the entire flash had finished. Right as I was rebooting I realized it said it was "formatting CACHE" but it was to late..I already started the reboot. So now my phone will get to the second loading screen that says "android" and then goes to a black screen. I have no recovery but can get into fastboot. I have the 1.6 SDK on my laptop, but have never used it, so the drivers aren't in place and plugging my phone in via USB does nothing.
I have read MANY posts about similar situations, but almost all of them involves using fastboot and ADB to push and install files, but how is that possible if I can't get ADB to work?? What else can be done via fastboot?? I know my phone isn't bricked, but not sure how to proceed from here.
I got a little further with my phone. I have ADB running on my laptop and I even got my computer to recognize the G1 as Android 1.0, but when I run ADB in a CD, it's not listing the phone. I am guessing because before this I wiped and never went and turned on USB de-bugging.
I ended up following the steps to downgrade, root, and ended up with a working phone.

Help! I cant flash Amons recovery

Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
_-..zKiLLA..-_ said:
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
Click to expand...
Click to collapse
what commands are you using to flash Amon_RA's recovery image? i also assume you're at the white bootloader screen when trying to flash Amon_RA's recovery image. also, to confirm root access, download the N1 Torch app and if it works, you're rooted.
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Cannot load what - fastboot or the ROM .img file? Do you have fastboot-windows.exe in the same directory as the rom image?-(not necessary if fastboot command works for you)
Type fastboot devices to double check your link between pc and phone. If not check usb cable & drivers.
Make sure ur unlock is right before flashing Amon. If you've rooted then you should see an unlocked-lock image (the the google Xscreen) while booting, or the N1 torch app method as mentioned above.
_-..zKiLLA..-_ said:
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Click to expand...
Click to collapse
Make sure you got to that white screen by pressing the trackball and not the volume rocker.
I renamed the recovery image to "recovery-RA-nexus-v1.7.0.img"
Code:
fastboot flash recovery recovery-RA-nexus-v1.7.0.img
Make sure you check
Code:
fastboot devices
and get your device number and also make sure you put it in the tools folder of the Android SDK
Make these steps
Boot ur phone into bootloader
1 Rename the img to recovery.img
2 Place the file in ur toolfolder where u have ur fastboot
3 Rightclik on toolfolder+Shift choose open cmd here
4 write fastboot devices to be shure u are connected
5 then write fastboot flash recovery recovery.img
hi,I have the problem too.I try many times but still stuck TRIANGLE WITH !.when I do recovery image
the screen come up "sending 'recovery"3948 kb.....ok
writing' recovery'......ok
sending 'recovery"3948 kb.....ok
writing' recovery'......ok
Click to expand...
Click to collapse
Code:
fastboot reboot
Finally got Amon_Ra's recovery to install
I started with a stock N1 with froyo
had a few stumbles along the way and lots of searching...lots and lots lol
using the how-to on the cyanogen page I went to the letter as ive never used ADB
So I installed the Latest Android SDK to get the ADB and Fastboot.
verified connection with "adb devices" command and so on
when I tried to flash amons the first time I got an error saying it couldn't open the file.
I checked to see if i had Super user with the LED flashlight app and I did not so I downloaded Super boot and it worked like a charm
tried again and got the same cannot open error.
I renamed the recovery image back to the original file name and triple checked everything else which didnt help.
at this point it was late and i was exhausted so my memory is fuzzy
but i had a few more issues and finally I installed the clock work app and installed clockwork recovery i then used that to flash amons because that is what i was familiar with from my G1 days.
I do remember I had to go into fast boot and select clear storage. I think thats what caused my N1 to hang on reboot after the ROM was flashed.
But It may have even been what caused my issues with the recovery image.

ROM doesn't start, recovery fails, fastboot not recognized by PC

Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?
What ROM u trying to flash? Some ROMs need some base files. You can even install a new Recovry Image through Recovery Console. Thats what I did
OK, What SPL you have right now...
Once you flash new SPL, old nandroid might not work properly as the partition layout has been changed....
Let us know the SPL you have now, sometimes if the phone is not getting recognized..then you have some old driver installed, try to see if that's the issue...
ms93 said:
Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?
Click to expand...
Click to collapse
I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.
There are other new and safe method to achieve the same or more then what you are trying to achieve with Haykuro SPL...see here..Custom MTD
But anyhow you are stuck with it...when you say Phone is not getting recognized..try restarting the phone in fastboot mode while connected to PC...when you are pressing back button are you getting fastboot..
I am not a good person to suggest something on this...If I would have been in your place I would have flashed DREAMIMG.nbh file and would have started from start....but wait till somebody better will tell you how to recover the device....
ms93 said:
I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.
Click to expand...
Click to collapse
G1sanju, I don't know what to say!
You saved my phone
Flashing DREAMIMG.nbh helped, phone has booted
OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.
DREAMIMG.nbh is an default image for G1, so it remove root access and leave the phone with the stock image...now you have 1.x radio and stock SPL...flashing haykuro SPL right now can brick your phone....
unlocker.com has some good guide to get the root access if you are looking for it....
Do not flash the Haykuro SPL or DangerSPL......That's of no use now....also there are chances that it can brick your phone....
Use Safe SPL...1.33.2003 those are full engineering SPL with fastboot access....
use CustomMTD to get the increase size as mentioned in my post above...
ms93 said:
OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.
Click to expand...
Click to collapse
I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.
Its great that you have used customMTD rather then Haykuro SPL...this is safe method....I just warned you because that's a very common way to brick the phone....flashing NBH and then installing SPL assuming you have the correct radio is a very common way of bricking the phone...
Also if you are playing with SPL and radio's then its advisable to erase the recovery first...then do the install from fastboot and then reinstall recovery...
ms93 said:
I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.
Click to expand...
Click to collapse

[Q] So my phone is bricked...

First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Uh, did you remove the back cover and remove/replace the battery?
Glycerin50 said:
First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Click to expand...
Click to collapse
Rom manager has a habit of breaking recoveries. If you can get into fastboot you can flash a new recovery from there. If you have an engineering spl that is. Need your info from fastboot. Do you have danger spl? Amonra has guides on how to flash from fastboot. Get his 1.7.0 and fastboot flash it. You dont sound bricked.
http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
Ok been a while ,sorry! I am still "bricked" (or at least i think i am). Yes i have taken out the battery and putting it back in.
@Johnson: Yes so i have read! A little to late, My info from fastboot:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA11000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
I'll go to that tutorial ,see if i can figure it out. Thanks for the help!
EDIT: So, ive read it... But its not clear to me. Do i need to open a terminal like program on my mac and just type in:
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
Or do i need to connect with my phone somehow (besides USB)
Yes, boot in to the SPl (you might need to enable fastboot in there, just poke stuff), then fire up Terminal.app, cd to the /tools directory where the SDK is installed, then issue the commands.
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Boot to fastboot mode. Should tell u how on amonra's page. Put recovery in tools folder of your sdk. Then open command prompt on PC and type: fastboot devices hit enter. Should get a serial number. CD to tools folder and type fastboot flash image command in thread
Sent from my HTC Magic SparksMod using XDA App
Glycerin50 said:
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Click to expand...
Click to collapse
Yes, the SPL is the bootloader (camera+power). To open the terminal, got to Applications > Utilities > Terminal.
ok, this is getting more and more understandable to me
Just where is this tools SDK folder. Will this apear on my pc when i plug my phone while i bootloader? or do i need to download some more stuff for this all to work on my pc...
U will need to look up how to install sdk on your computer. Its another program u need to control your phone with the PC. Called adb. Android debugging bridge
Sent from my HTC Magic SparksMod using XDA App
I don't think that fastboot comes with the SDK. There is fastboot-mac zip file somewhere out there... I can't remember where I got mine from, but there is one here http://developer.htc.com/adp.html
Put the file somewhere on your mac and use the terminal program in your applications/utilites folder to access it. You should be a little familiar with Linux to use it If you want to get fancy, put it in /usr/sbin or somewhere in your $path.
The SDK kit is good too, especially adb.
EDIT:
Here are a few good threads to get you headed down the path to flash-a-rama. Most of the commands are the same, regardless of platform, but the installation procedure will vary, i.e., fastboot erase system -w does the same thing on any platform.
http://forum.xda-developers.com/showthread.php?t=517874
http://forum.xda-developers.com/showthread.php?t=532719
Lastly this thread should be required reading... http://forum.xda-developers.com/showthread.php?t=655097
SUCCES! YEAH!!! Thank you guys so much! While reading your posts and all the guides i decided to get into bootcamp (windows on mac) and do it all there.
It was way easy to install and ive setup adb and SDK easy and used fastboot to flash Amon Ra's recovery!
It installed within seconds and from recovery i did a fresh wipe and installed my 5.0.8 cyanogen.
Right now it booting up for the first time as i typ and i think its going to boot.... Yes, it takes a long time the first time.
Yes, it works!
Thank you guys again!
Tobias

[Q] Fastboot.

Tried to install Cyanogen 6.1... It failed.
From there the device booted up normally on a fresh start, but I tried to recover my backup and that is where everything got all messed up.
Im stuck on the G1 screen.
Ive gotten it to the fastboot mode and Im downloading what I think I need to get my phone working again. Ive downloaded the Andriod 1.6 image from the HTC website. Do I need the recovery? I just want 1.6 until I have time to try and get Cyanogen installed.
Im currently installing JDK for the Andriod SDK.
Am I headed in the right direction?
I was using ROM Manager with Clockwork Mod. My old ROM was Super E... Not sure what version, but it was Andriod 2.1
What radio/spl do u have?
johnson8cyl said:
What radio/spl do u have?
Click to expand...
Click to collapse
2.22.19.26I
Tbry said:
2.22.19.26I
Click to expand...
Click to collapse
And spl? Do u have and eng spl? (S-off). If so u could fastboot erase your system and try to flash the rom through recovery. And fastboot flash a recovery of your choice first. Have u tried going on ezterry's thread with the new radio/spl and going that route?
Not sure what the version of the SPL is, but I know it is off. I'll check his thread out and give it a try. I might end up finding someone who actually knows what they are doing, or buying the Nexus S.
Ok. If u follow his thread exactly and fastboot flash the radio/recovery/spl u should end up with everything as described in the thread and be able to move on with cm6 with appropriate kernel. Alternatively u could boot into fastboot and open up your terminal on your computer and type in code to fastboot recovery of your choice (after it's download and put in sdk/tools folder on your PC) he has amonra link in his thread for download . Then type fastboot erase system -w (hit enter). When it's done type fastboot erase boot (hit enter). Then power down. Power back into recovery with the rom on your sdcard and flash away.
That is actually what I'm trying to do. Its just about my only option at this point.
Im having problems getting everything set up correctly though.
What are u having problems setting up?
I installed Andriod SDK, seems to be working.
Downloaded the drivers, which seems to have stopped my computer from seeing the phone.
I downloaded the Fastboot.exe, tried to run it but it cannot find ADB.dll ( Pretty sure thats what it was.)
I was basically following the steps on the cyanogen wiki.
When I have some time, I will try the Fastboot for noobs guide.
I think I followed a guide in androiddevelopers.com or something like that. If I find it again ill post a link. I don't think I ran a fastboot exe file though. Just have it in my androidsdk/tools folder. Added the variable to my paths and was good to go. Not at my PC currently though.
Edit: developer.android.com/sdk/
I believe is what I followed
http://forum.xda-developers.com/showthread.php?t=532719
Following this for fastboot.
I cannot update anything. Home + power doesnt do anything.
Only thing I can access is fastboot mode.
Fortunately my radio is up to date, so I assume my SPL is as well.
Going to attempt to try the fastboot step, once I can get the SDK working correctly
edit: I knew if I spent enough time working at it that I'd get it working.
Only problem now is getting my device to be listed.
Edit2: at first when I entered fastboot mode, I would get the "Add new hardware" for the device "Andriod 1.0"
It now says "andriod bootloader interface"
I feel like I'm so close. I'm going to keep playing with it, but what can I do to get my device listed when I type the command "Fastboot devices"?
Edit 3: Awesome. I got fastboot to work and my phone is recognized. Only problem now is getting my SD card reader to work so I can put the proper files on
Final edit: MY phone is killing SD cards for some reason. Don't know what to do
Got the SD cards to work, for some reason though, some of the commands are not working. When I type fastboot shell, I just get the usage doc.
When I do fastboot update, I get the following: error: failed to load 'update.zip'
What are u trying to do in fastboot?
Sent from my T-Mobile myTouch 3G using XDA App
Well, I fixed my phone. Back to its original state.
I guess my only question at this point my only question is if I switch to Cyanogen 6.1, will it be less buggy than my Super E ROM?
For anyone wondering, Holding home + end for about 25 seconds is what I did. From there I just went to nandriod and tried to recover the same backup that gave me the problem.
I would say no. It will not be less buggy. U can always flash and try different roms though for experiment sake. Glad u got it back up
Sent from my T-Mobile myTouch 3G using XDA App

Categories

Resources